From: Christoph Hellwig <hch@lst.de>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com,
Christoph Hellwig <hch@lst.de>, Milosz Tanski <milosz@adfin.com>
Subject: Re: preadv2/pwritev2 updates
Date: Thu, 2 Oct 2014 13:31:23 +0200 [thread overview]
Message-ID: <20141002113123.GB32112@lst.de> (raw)
In-Reply-To: <20141001222637.GU4758@dastard>
On Thu, Oct 02, 2014 at 08:26:37AM +1000, Dave Chinner wrote:
> On Wed, Oct 01, 2014 at 11:04:51PM +0200, Christoph Hellwig wrote:
> > Hi Miklos,
> >
> > attached are the patches that go on top of your
> > "[RFC v3 0/4] vfs: Non-blockling buffered fs read (page cache only)"
> > series. The first one adds RWF_NONBLOCK to XFS, the other two
> > add a new RWF_DSYNC flag that adds a per-operation O_DSYNC flag.
>
> Christoph, any plans to add these new syscalls to xfs_io and
> data integrity tests for the new RWF_DSYNC flag?
I've got some hacked up xfs_io support, but Milosz was planning a
slight revision of the syscall interface that I'm still waiting for.
How would you want to automatically test for data integrity? That requires
a powerfail or crash unfortunately and we don't have good infrastructure
for that yet. I've tested it by adding a printk that RWF_DSYNC triggers
the same code path as O_DSYNC.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@lst.de>, Milosz Tanski <milosz@adfin.com>,
linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: preadv2/pwritev2 updates
Date: Thu, 2 Oct 2014 13:31:23 +0200 [thread overview]
Message-ID: <20141002113123.GB32112@lst.de> (raw)
In-Reply-To: <20141001222637.GU4758@dastard>
On Thu, Oct 02, 2014 at 08:26:37AM +1000, Dave Chinner wrote:
> On Wed, Oct 01, 2014 at 11:04:51PM +0200, Christoph Hellwig wrote:
> > Hi Miklos,
> >
> > attached are the patches that go on top of your
> > "[RFC v3 0/4] vfs: Non-blockling buffered fs read (page cache only)"
> > series. The first one adds RWF_NONBLOCK to XFS, the other two
> > add a new RWF_DSYNC flag that adds a per-operation O_DSYNC flag.
>
> Christoph, any plans to add these new syscalls to xfs_io and
> data integrity tests for the new RWF_DSYNC flag?
I've got some hacked up xfs_io support, but Milosz was planning a
slight revision of the syscall interface that I'm still waiting for.
How would you want to automatically test for data integrity? That requires
a powerfail or crash unfortunately and we don't have good infrastructure
for that yet. I've tested it by adding a printk that RWF_DSYNC triggers
the same code path as O_DSYNC.
next prev parent reply other threads:[~2014-10-02 11:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 21:04 preadv2/pwritev2 updates Christoph Hellwig
2014-10-01 21:04 ` Christoph Hellwig
2014-10-01 21:04 ` [PATCH 1/3] xfs: add RWF_NONBLOCK support Christoph Hellwig
2014-10-01 21:04 ` Christoph Hellwig
2014-10-01 22:23 ` Dave Chinner
2014-10-01 22:23 ` Dave Chinner
2014-10-02 11:29 ` Christoph Hellwig
2014-10-02 11:29 ` Christoph Hellwig
2014-10-02 17:33 ` [PATCH 1/3 v2] " Christoph Hellwig
2014-10-01 21:04 ` [PATCH 2/3] fs: pass iocb to generic_write_sync Christoph Hellwig
2014-10-01 21:04 ` Christoph Hellwig
2014-10-01 21:04 ` [PATCH 3/3] fs: add a flag for per-operation O_DSYNC semantics Christoph Hellwig
2014-10-01 21:04 ` Christoph Hellwig
2014-10-01 22:26 ` preadv2/pwritev2 updates Dave Chinner
2014-10-01 22:26 ` Dave Chinner
2014-10-02 11:31 ` Christoph Hellwig [this message]
2014-10-02 11:31 ` Christoph Hellwig
2014-10-02 21:05 ` Dave Chinner
2014-10-02 21:05 ` Dave Chinner
2014-10-08 2:58 ` Milosz Tanski
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=20141002113123.GB32112@lst.de \
--to=hch@lst.de \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=milosz@adfin.com \
--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.