From: Christoph Hellwig <hch@lst.de>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
Alexander Viro <viro@zeniv.linux.org.uk>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: [PATCH 09/10] fs: add RWF_DSYNC aand RWF_SYNC
Date: Tue, 9 Aug 2016 10:15:57 +0200 [thread overview]
Message-ID: <20160809081557.GA10564@lst.de> (raw)
In-Reply-To: <CAKgNAkjza2eZnS7bzmvg1nB_jLmtk1N-o=uusD_hBo20sHTyaA@mail.gmail.com>
Hi Michael,
On Sun, Aug 07, 2016 at 07:45:03AM +1000, Michael Kerrisk (man-pages) wrote:
> I've added some documentation for these flags to the man page, but in
> the process I realized that have a question. Do these flags provide
> equivalents of O_DSYNC and O_SYNC for the I/O operation, or for the
> file? What I mean is this: with, say, RWF_DSYNC, is it just the data
> written by this pwritev2() call that is synced to the underlying file,
> or is all dirty data for the file synced at that point?
You beat me to it - I'm overdue sending you updates for these flags.
The flags only affect the actual pwritev2 operation they are applied
to. That is only the range just written is guaranteed to be on
stable storage.
Btw, I was going to just send you a patch, but it seems your update
isn't out in the git tree yet, is it?
next prev parent reply other threads:[~2016-08-09 8:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 15:51 add RWF_(D)SYNC flag to preadv2/pwritev2 V2 Christoph Hellwig
2016-04-07 15:51 ` Christoph Hellwig
[not found] ` <1460044324-5298-1-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2016-04-07 15:51 ` [PATCH 01/10] filemap: remove pos variables in generic_file_read_iter Christoph Hellwig
2016-04-07 15:51 ` Christoph Hellwig
2016-04-07 15:51 ` [PATCH 02/10] filemap: remove the pos argument to generic_file_direct_write Christoph Hellwig
2016-04-07 15:51 ` Christoph Hellwig
2016-04-07 15:51 ` [PATCH 04/10] direct-io: eliminate the offset argument to ->direct_IO Christoph Hellwig
2016-04-07 15:51 ` Christoph Hellwig
2016-04-07 15:51 ` [PATCH 05/10] direct-io: remove the offset argument to dio_complete Christoph Hellwig
2016-04-07 15:51 ` Christoph Hellwig
2016-04-07 15:52 ` [PATCH 06/10] fs: add IOCB_SYNC and IOCB_DSYNC Christoph Hellwig
2016-04-07 15:52 ` Christoph Hellwig
2016-04-07 15:52 ` [PATCH 07/10] fs: simplify the generic_write_sync prototype Christoph Hellwig
2016-04-07 15:52 ` Christoph Hellwig
2016-04-07 15:52 ` [PATCH 09/10] fs: add RWF_DSYNC aand RWF_SYNC Christoph Hellwig
2016-04-07 15:52 ` Christoph Hellwig
2016-08-06 21:45 ` Michael Kerrisk (man-pages)
2016-08-09 8:15 ` Christoph Hellwig [this message]
[not found] ` <20160809081557.GA10564-jcswGhMUV9g@public.gmane.org>
2016-09-04 4:56 ` Michael Kerrisk (man-pages)
2016-09-04 4:56 ` Michael Kerrisk (man-pages)
2016-04-25 11:48 ` add RWF_(D)SYNC flag to preadv2/pwritev2 V2 Christoph Hellwig
2016-04-25 11:48 ` Christoph Hellwig
2016-04-07 15:51 ` [PATCH 03/10] xfs: eliminate the pos variable in xfs_file_dio_aio_write Christoph Hellwig
[not found] ` <1460044324-5298-4-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2016-04-07 22:31 ` Dave Chinner
2016-04-07 22:31 ` Dave Chinner
2016-04-07 22:43 ` Christoph Hellwig
2016-04-07 22:43 ` Christoph Hellwig
2016-04-07 22:50 ` Dave Chinner
2016-04-07 15:52 ` [PATCH 08/10] ceph: use generic_write_sync Christoph Hellwig
2016-04-07 15:52 ` [PATCH 10/10] nfsd: use RWF_SYNC Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2016-03-29 17:37 add RWF_(D)SYNC flag to preadv2/pwritev2 Christoph Hellwig
2016-03-29 17:37 ` [PATCH 09/10] fs: add RWF_DSYNC aand RWF_SYNC 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=20160809081557.GA10564@lst.de \
--to=hch@lst.de \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--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 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.