[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081129185645.GA20194@shareable.org>
Date: Sat, 29 Nov 2008 18:56:45 +0000
From: Jamie Lokier <jamie@...reable.org>
To: Jörn Engel <joern@...fs.org>
Cc: Matthew Wilcox <matthew@....cx>,
Andrew Morton <akpm@...ux-foundation.org>,
Christoph Hellwig <hch@...radead.org>,
Matthew Garrett <mjg@...hat.com>,
Randy Dunlap <randy.dunlap@...cle.com>,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
mingo@...hat.com, val.henson@...il.com
Subject: Re: [PATCH v2 2/2] relatime: Allow making relatime the default behaviour
Jörn Engel wrote:
> ...and check the tmpreaper manpage, you will notice that tmpreaper can
> be configured as well. So relatime has a default timeout of T and
> tmpreaper is configured to delete files after 1/2 T (never mind what T
> might be), the system breaks. Guessing a value of T that is good enough
> for everyone is a complicated business, so one configurable makes sense
> imo.
>
> One per mountpoint is rather silly, of course.
If it's configurable at all for tmpreaper (or similar), it should work
the same for tmpreaper in virtual machine containers. (Same as,
e.g. utsname is different in containers). If not now, someone will
have to patch it later. Each VM runs it's own tmpreaper, configured
usually by separate people.
It's probably simpler to make it per-mountpoint than a virtualised global.
I don't see why there is an objection to per-mountpoint.
Andrew Morton's syntax: mount /dev/foo /mnt/bar -o relatime=86400
looks natural to me.
-- Jamie
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists