|| ||Ingo Molnar <mingo-AT-elte.hu>|
|| ||Matthew Wilcox <matthew-AT-wil.cx>|
|| ||Re: [PATCH v2 2/2] relatime: Allow making relatime the default
|| ||Sat, 29 Nov 2008 22:41:19 +0100|
|| ||Andrew Morton <akpm-AT-linux-foundation.org>,
Matthew Garrett <mjg-AT-redhat.com>,
Jamie Lokier <jamie-AT-shareable.org>,
J?rn Engel <joern-AT-logfs.org>,
Christoph Hellwig <hch-AT-infradead.org>,
Randy Dunlap <randy.dunlap-AT-oracle.com>,
|| ||Article, Thread
* Matthew Wilcox <firstname.lastname@example.org> wrote:
> On Sat, Nov 29, 2008 at 12:32:20PM -0800, Andrew Morton wrote:
> > The standard, usual, expected way of modifying a filesystem's behaviour
> > is via mount options. This is also quite flexible.
> > Is there some extraordinary reason why the standard interface is not to
> > be used here?
> Because it would have to be managed (and consulted) per ... what?
> vfsmount? superblock? This is featuritis gone MAD.
> I'll take my bikeshed in teal, stippled with cornsilk.
Meanwhile, 10 years and counting, the Linux kernel still generates a
stupid write IO for every file read that apps do. Fortunately hardware
designers will get rid of rotating disks faster than we can fix our
glaring process problems in this space - but it's still a bit sad.
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
to post comments)