search for: aio_setup

On Fri, Mar 11, 2016 at 04:30:07PM +0900, Minchan Kim wrote: > From: Gioh Kim <gurugio at hanmail.net> > > The anon_inodes has already complete interfaces to create manage > many anonymous inodes but don't have interface to get > new inode. Other sub-modules can create anonymous inode > without creating and mounting it's own pseudo filesystem. IMO that's a bad

On Fri, Mar 11, 2016 at 04:30:07PM +0900, Minchan Kim wrote: > From: Gioh Kim <gurugio at hanmail.net> > > The anon_inodes has already complete interfaces to create manage > many anonymous inodes but don't have interface to get > new inode. Other sub-modules can create anonymous inode > without creating and mounting it's own pseudo filesystem. IMO that's a bad

...device found Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16) apm: disabled - APM is not SMP safe. Total HugeTLB memory allocated, 0 Starting kswapd VFS: Disk quotas vdquot_6.5.1 aio_setup: num_physpages = 32252 aio_setup: sizeof(struct page) = 60 Hugetlbfs mounted. pty: 2048 Unix98 ptys configured Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI ISAPNP enabled ttyS0 at 0x03f8 (irq = 4) is a 16550A Real Time Clock Driver v1.10e NET4: Frame Dive...

depends on "autoconf: regenerate configure scripts with 4.4 version" This series removes some of the really old deadwood from the tools build and makes some other things which are on their way out configurable at build time with a default depending on how far down the slope I judge them to be. * nuke in tree copy of libaio * nuke obsolete tools: xsview, miniterm, lomount & sv *

Hi, another issue I''m seeing with 3.0-rc2 and Xen is that there is an unexpectedly high amount of kernel reserved memory. I suspect that Linux allocates page table entries and corresponding data structures for the whole 6GB areas of the provided ''physical RAM map'' even though it has rather big unusable holes in it. [ 0.000000] BIOS-provided physical RAM map: [

...rned 0 after 5 usecs [ 38.150744] calling inotify_setup+0x0/0xd @ 1 [ 38.155250] initcall inotify_setup+0x0/0xd returned 0 after 0 usecs [ 38.161576] calling inotify_user_setup+0x0/0x9d @ 1 [ 38.166617] initcall inotify_user_setup+0x0/0x9d returned 0 after 13 usecs [ 38.173536] calling aio_setup+0x0/0x5f @ 1 [ 38.178541] initcall aio_setup+0x0/0x5f returned 0 after 739 usecs [ 38.184630] calling proc_locks_init+0x0/0x1a @ 1 [ 38.189397] initcall proc_locks_init+0x0/0x1a returned 0 after 1 usecs [ 38.195982] calling dquot_init+0x0/0xdd @ 1 [ 38.200315] VFS: Disk quotas dquot_6.5...

Lots of changes since v2, too much to remember or summarize. Please ignore patch 11/11, it's just for my testing. Rich.

...0 after 135 usecs [ 27.249539] calling dnotify_init+0x0/0x7b @ 1 [ 27.250138] initcall dnotify_init+0x0/0x7b returned 0 after 461 usecs [ 27.250300] calling inotify_user_setup+0x0/0x70 @ 1 [ 27.250848] initcall inotify_user_setup+0x0/0x70 returned 0 after 390 usecs [ 27.250982] calling aio_setup+0x0/0x7c @ 1 [ 27.251557] initcall aio_setup+0x0/0x7c returned 0 after 439 usecs [ 27.251690] calling proc_locks_init+0x0/0x22 @ 1 [ 27.251826] initcall proc_locks_init+0x0/0x22 returned 0 after 10 usecs [ 27.251960] calling init_sys32_ioctl+0x0/0x28 @ 1 [ 27.252262] initcall init_sys32...