All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Valerie Henson <val_henson@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Akkana Peck <akkana@shallowsky.com>,
	Mark Fasheh <mark.fasheh@oracle.com>,
	Jesse Barnes <jesse.barnes@intel.com>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Chris Wedgwood <cw@f00f.org>,
	jsipek@cs.sunysb.edu, Al Viro <viro@ftp.linux.org.uk>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [RFC] [PATCH] Relative lazy atime
Date: Sat, 5 Aug 2006 14:25:37 +0200	[thread overview]
Message-ID: <20060805122537.GA23239@lst.de> (raw)
In-Reply-To: <20060803063622.GB8631@goober>

On Wed, Aug 02, 2006 at 11:36:22PM -0700, Valerie Henson wrote:
> (Corrected Chris Wedgwood's name and email.)
> 
> My friend Akkana followed my advice to use noatime on one of her
> machines, but discovered that mutt was unusable because it always
> thought that new messages had arrived since the last time it had
> checked a folder (mbox format).  I thought this was a bummer, so I
> wrote a "relative lazy atime" patch which only updates the atime if
> the old atime was less than the ctime or mtime.  This is not the same
> as the lazy atime patch of yore[1], which maintained a list of inodes
> with dirty atimes and wrote them out on unmount.

Another idea, similar to how atime updates work in xfs currently might
be interesting:  Always update atime in core, but don't start a
transaction just for it - instead only flush it when you'd do it anyway,
that is another transaction or evicting the inode.


  parent reply	other threads:[~2006-08-05 12:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03  6:36 [RFC] [PATCH] Relative lazy atime Valerie Henson
2006-08-03 14:48 ` Matthew Wilcox
2006-08-05 12:25 ` Christoph Hellwig [this message]
2006-08-05 13:22   ` Arjan van de Ven
2006-08-09 14:03     ` Valerie Henson
2006-08-09 15:49       ` Erez Zadok
2006-08-10 12:27       ` Helge Hafting
2006-08-05 16:58   ` Dave Kleikamp
2006-08-05 17:04     ` Arjan van de Ven
2006-08-05 18:36       ` Chris Wedgwood
2006-08-05 22:22         ` Mark Fasheh
2006-08-05 23:06           ` David Lang
2006-08-05 23:28             ` dean gaudet
2006-08-06  0:11               ` Chris Wedgwood
2006-08-06  3:01               ` Matthew Wilcox
2006-08-09  6:39                 ` Valerie Henson
2006-08-09 12:21                   ` Jörn Engel
2006-08-09 12:21                     ` Jörn Engel
2006-08-09 12:58                     ` Dave Kleikamp
2006-08-09 12:58                       ` Dave Kleikamp
2006-08-10 11:34                     ` Frank van Maarseveen
2006-08-10 11:34                       ` Frank van Maarseveen
2006-08-10 17:28                   ` Bill Davidsen
2006-08-06  0:13             ` Mark Fasheh
     [not found] <6Gts4-6UM-1@gated-at.bofh.it>
     [not found] ` <6GxFs-4Tg-13@gated-at.bofh.it>
     [not found]   ` <6Gy8r-5Oh-11@gated-at.bofh.it>
     [not found]     ` <6Gze7-7oP-7@gated-at.bofh.it>
     [not found]       ` <6GCOJ-4fv-19@gated-at.bofh.it>
     [not found]         ` <6GDB1-5qX-3@gated-at.bofh.it>
     [not found]           ` <6GDKT-5Eb-37@gated-at.bofh.it>
     [not found]             ` <6GHbD-2hm-1@gated-at.bofh.it>
     [not found]               ` <6HQ3c-6Pf-9@gated-at.bofh.it>
     [not found]                 ` <6HVml-6DI-11@gated-at.bofh.it>
     [not found]                   ` <6Ih3l-5FP-1@gated-at.bofh.it>
2006-08-10 13:07                     ` Bodo Eggert
2006-08-10 13:07                       ` Bodo Eggert
  -- strict thread matches above, loose matches on Subject: below --
2006-08-03  6:29 Valerie Henson
2006-08-03  6:44 ` Josef Sipek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060805122537.GA23239@lst.de \
    --to=hch@lst.de \
    --cc=akkana@shallowsky.com \
    --cc=arjan@linux.intel.com \
    --cc=cw@f00f.org \
    --cc=jesse.barnes@intel.com \
    --cc=jsipek@cs.sunysb.edu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.fasheh@oracle.com \
    --cc=val_henson@linux.intel.com \
    --cc=viro@ftp.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.