All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs_io: add support for O_TMPFILE opens
Date: Fri, 21 Feb 2014 09:15:18 +1100	[thread overview]
Message-ID: <20140220221518.GR4916@dastard> (raw)
In-Reply-To: <20140220220000.GA17541@infradead.org>

On Thu, Feb 20, 2014 at 02:00:00PM -0800, Christoph Hellwig wrote:
> Add a new -T argument to the open command that supports using the
> O_TMPFILE flag.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>

Can you also push this into the main CLI interface similar to how
all the other open flags can be specified? i.e.

$ xfs_io -d -c "pwrite 0 4k" foo

will open "foo" with O_DIRECT. Be nice just to be able to do

$ xfs_io -dT -c "pwrite 0 4k" foo/

to be able to test O_TMPFILE functionality

FWIW, any plans to add a "link" command to be able to link the
tmpfile into the namespace once it is created?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-02-20 22:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 22:00 [PATCH] xfs_io: add support for O_TMPFILE opens Christoph Hellwig
2014-02-20 22:15 ` Dave Chinner [this message]
2014-02-20 22:40   ` Christoph Hellwig
2014-02-21  0:16 ` Shaun Gosse
2014-02-21  0:20   ` Christoph Hellwig
2014-02-21  0:30 ` [PATCH v2] " Christoph Hellwig
2014-02-23 21:01   ` Dave Chinner
2014-02-21  0:49 ` [PATCH] xfs_io: add support for flink Christoph Hellwig
2014-02-23 21:06   ` Dave Chinner
2014-02-25 19:52   ` [PATCH v2] " Christoph Hellwig
2014-02-25 23:35     ` Dave Chinner
2014-03-13 10:09       ` Christoph Hellwig
2014-03-13 10:21         ` Dave Chinner
2014-03-13 10:42           ` Dave Chinner

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=20140220221518.GR4916@dastard \
    --to=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=xfs@oss.sgi.com \
    /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.