Messages in this thread |  | | Subject | Re: [RFC] CPU controllers? | | From | Mike Galbraith <> | | Date | Mon, 19 Jun 2006 08:28:45 +0200 |
| |
This is kinda OT for this thread, but here's another example of where the IO can easily foil CPU distribution plans. I wonder how many folks get nailed by /proc being mounted without noatime,nodiratime like I just apparently did.
top D E29B4928 0 10174 8510 (NOTLB) d2f63c4c 00100100 00200200 e29b4928 ea07f3c0 f1510c40 000f6e66 d2f63000 d2f63000 ed88c550 f1510c40 000f6e66 d2f63000 d2f63000 ed062220 ed88c550 d2f63c70 b139a97b ed062224 efef8df8 ed062224 ed88c550 d2f63000 0000385a Call Trace: [<b139a97b>] __mutex_lock_slowpath+0x59/0xb0 [<b139a9d7>] .text.lock.mutex+0x5/0x14 [<b10bb24f>] __log_wait_for_space+0x53/0xb4 [<b10b67b4>] start_this_handle+0x100/0x617 [<b10b6d86>] journal_start+0xbb/0xe0 [<b10ae10e>] ext3_journal_start_sb+0x29/0x4a [<b10a8d9f>] ext3_dirty_inode+0x2a/0xaf [<b1080171>] __mark_inode_dirty+0x2a/0x19e [<b107784a>] touch_atime+0x79/0x9f [<b103fda5>] do_generic_mapping_read+0x370/0x480 [<b1040747>] __generic_file_aio_read+0xf0/0x205 [<b1040896>] generic_file_aio_read+0x3a/0x46 [<b105d919>] do_sync_read+0xbb/0xf1 [<b105e2c1>] vfs_read+0xa4/0x166 [<b105e6c1>] sys_read+0x3d/0x64 [<b1002e1b>] syscall_call+0x7/0xb
netdaemon D EC84ED04 0 7696 1 7711 7695 (NOTLB) efef8dec 00000000 efef8000 ec84ed04 efef8e00 402cecc0 000f6e68 efef8000 efef8000 ed617030 402cecc0 000f6e68 efef8000 efef8000 ed062220 ed617030 efef8e10 b139a97b ed062224 ed062224 d2f63c58 ed617030 efef8000 0000385a Call Trace: [<b139a97b>] __mutex_lock_slowpath+0x59/0xb0 [<b139a9d7>] .text.lock.mutex+0x5/0x14 [<b10bb24f>] __log_wait_for_space+0x53/0xb4 [<b10b67b4>] start_this_handle+0x100/0x617 [<b10b6d86>] journal_start+0xbb/0xe0 [<b10ae10e>] ext3_journal_start_sb+0x29/0x4a [<b10a8d9f>] ext3_dirty_inode+0x2a/0xaf [<b1080171>] __mark_inode_dirty+0x2a/0x19e [<b107784a>] touch_atime+0x79/0x9f [<b106fc08>] vfs_readdir+0x91/0x93 [<b106fc6a>] sys_getdents64+0x60/0xa7 [<b1002e1b>] syscall_call+0x7/0xb
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |