[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081127223514.GP25548@parisc-linux.org>
Date: Thu, 27 Nov 2008 15:35:14 -0700
From: Matthew Wilcox <matthew@....cx>
To: Andreas Dilger <adilger@....com>
Cc: Matthew Garrett <mjg@...hat.com>,
Christoph Hellwig <hch@...radead.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
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 v4] relatime: Make relatime smarter
On Thu, Nov 27, 2008 at 03:08:39PM -0700, Andreas Dilger wrote:
> On Nov 27, 2008 17:58 +0000, Matthew Garrett wrote:
> > + relatime_interval=
> > + [FS] relative atime update frequency, in seconds.
> > + (default: 1 day: 86400 seconds)
>
> The one problem with a 1-day default is that cron jobs like updatedb will
> revert to updating the atime on every single file every day. It would be
> better to make it slightly more than 1 day (e.g. 25h) to avoid this and
> at least defer atime updates to every other day for files that are not
> otherwise accessed except by cron.
Doesn't updatedb only access directories, not files? I don't think
relatime implies nodiratime, but certainly the two could both be
specified, and that would fix one of the updatedb problems. Are there
any other common cronjobs you're concerned about?
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
--
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