From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
hch@lst.de, rdorr@microsoft.com
Subject: [PATCH 0/4 V2] iomap: Use FUA for O_DSYNC DIO writes
Date: Wed, 18 Apr 2018 14:08:24 +1000 [thread overview]
Message-ID: <20180418040828.18165-1-david@fromorbit.com> (raw)
Hi folks,
This is the latest version of the "use FUA for DIO writes" patchset
that was last posted here:
https://marc.info/?l=linux-xfs&m=152213446528167&w=2
Functionality and performance is the same as the previous version.
Changes in this version address Christoph's review comments.
Version 2:
- Fixed comment typos in first patch
- simplified iomap_dio_complete_work()
- changed IOMAP_DIO_WRITE_SYNC to IOMAP_DIO_NEED_SYNC
- split blk_queue_fua() into it's own patch
- fixed formatting issue in last patch
- update bio->io_opf directly rather than use bio_set_op_attrs()
- Updated comment to mention we try to use FUA optimistically.
Cheers,
Dave.
next reply other threads:[~2018-04-18 4:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 4:08 Dave Chinner [this message]
2018-04-18 4:08 ` [PATCH 1/4] xfs: move generic_write_sync calls inwards Dave Chinner
2018-04-18 4:08 ` [PATCH 2/4] iomap: iomap_dio_rw() handles all sync writes Dave Chinner
2018-04-21 13:03 ` Jan Kara
2018-05-02 2:45 ` Dave Chinner
2018-05-02 14:27 ` Robert Dorr
2018-05-02 14:27 ` Robert Dorr
2018-05-03 13:34 ` Jan Kara
2018-05-03 12:51 ` Jan Kara
2018-04-18 4:08 ` [PATCH 3/4] blk: add blk_queue_fua() helper function Dave Chinner
2018-04-18 10:34 ` Christoph Hellwig
2018-04-18 12:18 ` Matthew Wilcox
2018-04-18 14:23 ` Jens Axboe
2018-04-18 4:08 ` [PATCH 4/4] iomap: Use FUA for pure data O_DSYNC DIO writes Dave Chinner
2018-04-21 12:54 ` Jan Kara
2018-04-24 17:34 ` Christoph Hellwig
2018-04-24 22:07 ` Holger Hoffstätte
2018-04-25 5:20 ` Christoph Hellwig
2018-04-25 5:20 ` Christoph Hellwig
2018-04-25 13:02 ` Jan Kara
2018-04-25 13:02 ` Jan Kara
2018-05-02 2:34 ` 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=20180418040828.18165-1-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=rdorr@microsoft.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.