[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1155128301.10228.2.camel@kleikamp.austin.ibm.com>
Date: Wed, 09 Aug 2006 07:58:20 -0500
From: Dave Kleikamp <shaggy@...tin.ibm.com>
To: Jörn Engel <joern@...nheim.fh-wedel.de>
Cc: Valerie Henson <val_henson@...ux.intel.com>,
Matthew Wilcox <matthew@....cx>, dean gaudet <dean@...tic.org>,
David Lang <dlang@...italinsight.com>,
Mark Fasheh <mark.fasheh@...cle.com>,
Chris Wedgwood <cw@...f.org>,
Arjan van de Ven <arjan@...ux.intel.com>,
Christoph Hellwig <hch@....de>, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, Akkana Peck <akkana@...llowsky.com>,
Jesse Barnes <jesse.barnes@...el.com>, jsipek@...sunysb.edu,
Al Viro <viro@....linux.org.uk>
Subject: Re: [RFC] [PATCH] Relative lazy atime
On Wed, 2006-08-09 at 14:21 +0200, Jörn Engel wrote:
> 1. standard
> Every read access to a file/directory causes an atime update.
>
> 2. nodiratime
> Every read access to a non-directory causes an atime update.
>
> 3. lazy atime
> The first read access to a file/directory causes an atime update.
>
> 4. noatime
> No read access to a file/directory causes an atime update.
>
> In comparison, lazy atime will cause more atime updates for
> directories and vastly fewer for non-directories.
Using nodiratime and lazy atime together would probably be the best
option for those that only want atime for mutt/shell mail notification.
> Effectively atime
> is turned into little more than a flag, stating whether the file was
> ever read since the last write to it. And it appears as if neither
> mutt nor the shell use atime for more than this flagging purpose, so I
> am rather fond of the idea.
>
> Jörn
>
--
David Kleikamp
IBM Linux Technology Center
-
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