linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Christoph Hellwig <hch@lst.de>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] add a FMODE flag to make XFS invisible I/O less hacky
Date: Sun, 30 Nov 2008 10:16:04 +0100	[thread overview]
Message-ID: <20081130091603.GA3315@lst.de> (raw)
In-Reply-To: <20081128113052.GS28946@ZenIV.linux.org.uk>

On Fri, Nov 28, 2008 at 11:30:52AM +0000, Al Viro wrote:
> On Fri, Nov 28, 2008 at 12:24:02PM +0100, Christoph Hellwig wrote:
> > XFS has a mode called invisble I/O that doesn't update any of the
> > timestamps.  It's used for HSM-style applications and exposed through
> > the nasty open by handle ioctl.
> > 
> > Instead of doing directly assignment of file operations that set an
> > internal flag for it add a new FMODE_INVISIBLE flag that we can check
> > in the normal file operations.
> 
> Seeing that it's similar to O_NOATIME, why not do it in O_... space?

For now I just want to get rid of the horrible hack in XFS.  Adding this
as a user-visible feature might be a good idea that those who need it
can submit.


  reply	other threads:[~2008-11-30  9:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-28 11:24 [PATCH] add a FMODE flag to make XFS invisible I/O less hacky Christoph Hellwig
2008-11-28 11:30 ` Al Viro
2008-11-30  9:16   ` Christoph Hellwig [this message]
2008-12-02 10:19     ` Christoph Hellwig
2008-11-28 22:58 ` Andreas Dilger
2008-11-30  9:18   ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2008-12-03 17:45 Christoph Hellwig

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=20081130091603.GA3315@lst.de \
    --to=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@ZenIV.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).