Messages in this thread | | | Date | Sat, 04 Aug 2007 16:28:17 -0400 | From | Jeff Garzik <> | Subject | Re: [PATCH 00/23] per device dirty throttling -v8 |
| |
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 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/
| |