On Wed, May 21, 2008 at 07:46:17AM +1000, David Chinner (dgc@xxxxxxx) wrote: > Oh, god no. Let's not put the inode_lock right at the top of > the VM page cleaning path. We don't need to modify inode state, > the superblock dirty lists, etc - all we need to do is write > dirty pages on a given mapping in a more efficient manner. I'm not advocating that, but having swap on reclaim does not hurt anyone, this is essentially the same, but with different underlying storage. System will do that anyway sooner or later during usual writeback, which in turn can be a result of the same reclaim... -- Evgeniy Polyakov -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
