Re: [PATCH 00/23] per device dirty throttling -v8
From: Jeff Garzik <hidden>
Date: 2007-08-04 20:28:43
Also in:
lkml
Alan Cox wrote:
In some setups it will and in others it won't. Nor is it the only application that has this requirement. Ext3 currently is a standards compliant file system. Turn off atime and its very non standards compliant, turn to relatime and its not standards compliant but nobody will break (which is good)
Linux has always been a "POSIX unless its stupid" type of system. For the upstream kernel, we should do the right thing -- noatime by default -- but allow distros and people that care about rigid compliance to easily change the default. (from another message)
If you want to sort this in Fedora for example you just need to package and announce a desktop-tuning rpm which makes the relevant updates on install and reverses them on remove. Stick the scheduler/vm tuning values in as well and the disk queue tweaks. Regardless of the kernel defaults people will install such a package en-mass...
<chuckle> Sounds like an effective idea :) Though strictly in the context of atime vs. noatime, servers benefit from that too, not just desktop. Jeff -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>