public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Cesar Eduardo Barros <cesarb@nitnet.com.br>
Cc: Christoph Hellwig <hch@infradead.org>,
	linux-kernel@vger.kernel.org, Alexander Viro <viro@math.psu.edu>
Subject: Re: [PATCH] O_NOATIME support
Date: Mon, 14 Jun 2004 15:03:56 +0100	[thread overview]
Message-ID: <20040614140356.GA21349@infradead.org> (raw)
In-Reply-To: <20040614134652.GA1961@flower.home.cesarb.net>

On Mon, Jun 14, 2004 at 10:46:52AM -0300, Cesar Eduardo Barros wrote:
> I don't see why preserving the mtime and ctime would be necessary, since
> to move a file away you either don't touch it (using rename) or only
> read and unlink it (to write to a tape or other filesystem, and you can
> save the atime and mtime while doing it). So O_NOATIME is enough for
> both behaviours.

Maybe some day the file needs to come back from the tape ;-)  Or rather
in the HSM scenario a part of the file.


  reply	other threads:[~2004-06-14 14:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-12  1:11 [PATCH] O_NOATIME support Cesar Eduardo Barros
2004-06-12 16:44 ` Bernd Eckenfels
2004-06-12 18:09   ` Chris Wedgwood
2004-06-12 18:22     ` Bernd Eckenfels
2004-06-14  9:55 ` Christoph Hellwig
2004-06-14 13:46   ` Cesar Eduardo Barros
2004-06-14 14:03     ` Christoph Hellwig [this message]
2004-06-14 19:25       ` Cesar Eduardo Barros
2004-06-14 16:57     ` David Lang
2004-06-14 19:34       ` Cesar Eduardo Barros
2004-06-14 15:38   ` Paul Jackson
2004-06-14 21:12 ` Alexandre Oliva
2004-06-14 21:58   ` Valdis.Kletnieks
2004-06-14 22:09   ` Matthias Schniedermeyer
2004-06-15 19:02     ` Alexandre Oliva
2004-06-16  1:49       ` Horst von Brand
2004-06-14 22:40   ` Cesar Eduardo Barros
2004-06-14 23:14     ` Bernd Eckenfels
2004-06-15 19:01     ` Alexandre Oliva
2004-06-15 19:32       ` Matthias Schniedermeyer
2004-06-15 22:03         ` Paul Jackson
2004-06-16  6:21           ` Matthias Schniedermeyer

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=20040614140356.GA21349@infradead.org \
    --to=hch@infradead.org \
    --cc=cesarb@nitnet.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox