Re: [PATCH 0/6] writeback: moving expire targets forbackground/kupdate works

[Christoph Hellwig]

Hi Wu,

if you're queueing up writeback changes can you look into splitting
inode_wb_list_lock as it was done in earlier versions of the inode
scalability patches?  Especially if we don't get the I/O less
balance_dirty_pages in ASAP it'll at least allows us to scale the
busy waiting for the list manipulationes to one CPU per BDI.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/