linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@infradead.org>, linux-block@vger.kernel.org
Subject: Re: [PATCHSET] Add support for simplified async direct-io
Date: Thu, 17 Nov 2016 04:50:37 -0800	[thread overview]
Message-ID: <20161117125037.GB14814@infradead.org> (raw)
In-Reply-To: <c2e20890-16ce-a3bd-c696-c53ae14a583a@kernel.dk>

On Wed, Nov 16, 2016 at 09:43:57PM -0700, Jens Axboe wrote:
> OK, I'm getting reasonably happy with it now:
> 
> http://git.kernel.dk/cgit/linux-block/log/?h=for-4.10/hch-dio
> 
> Sharing the FUA setting to avoid the manual flush between the two, and
> removing the remnants of SYNC support from __blkdev_direct_IO().
> 
> I'll fire off some overnight testing now and leave it for the day.

This looks reasonable, a couple questions and comments:

 - why the 8 * BIO_MAX_PAGES in the call to iov_iter_npages,
   that probably needs a comment
 - I'll probably need to write up a proper changelog and fold
   in at least the multi_bio patch.
 - I'd just return the op from dio_bio_set_write_op instead of
   passing the bio, that reads a lot easier.
 - I should probably get rid of blkdev_dio_pool in favour
   of bio_kmalloc

I can look into doing these fixups this afternoon and prepare a tre
for you.

  reply	other threads:[~2016-11-17 12:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14 17:28 [PATCHSET] Add support for simplified async direct-io Jens Axboe
2016-11-14 17:28 ` [PATCH 1/2] block: support any sized IO for simplified bdev direct-io Jens Axboe
2016-11-14 17:28 ` [PATCH 2/2] block: add support for async simple direct-io for bdevs Jens Axboe
2016-11-14 17:37 ` [PATCHSET] Add support for simplified async direct-io Christoph Hellwig
2016-11-14 17:47   ` Jens Axboe
2016-11-14 18:00     ` Christoph Hellwig
2016-11-14 18:02       ` Jens Axboe
2016-11-14 18:05         ` Christoph Hellwig
2016-11-14 18:08           ` Jens Axboe
2016-11-14 18:11             ` Christoph Hellwig
2016-11-14 18:17               ` Jens Axboe
2016-11-15 13:58                 ` Christoph Hellwig
2016-11-16 16:09               ` Jens Axboe
2016-11-16 16:31                 ` Christoph Hellwig
2016-11-16 16:57                   ` Jens Axboe
2016-11-16 17:16                     ` Christoph Hellwig
2016-11-16 20:02                       ` Jens Axboe
2016-11-16 20:36                         ` Jens Axboe
2016-11-16 20:51                           ` Jens Axboe
2016-11-17  3:44                             ` Jens Axboe
2016-11-17  4:43                         ` Jens Axboe
2016-11-17 12:50                           ` Christoph Hellwig [this message]
2016-11-17 13:25                             ` Jens Axboe
2016-11-17 15:03                               ` Jens Axboe
2016-11-17 15:16                                 ` Christoph Hellwig
2016-11-17 20:17                                 ` Christoph Hellwig
2016-11-17 20:30                                   ` Jens Axboe
2016-11-17 21:04                                     ` Christoph Hellwig
2016-11-17 21:06                                       ` Jens Axboe
2016-11-17 12:46                         ` Christoph Hellwig
2016-11-17 13:26                           ` Jens Axboe

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=20161117125037.GB14814@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    /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).