From: Jens Axboe <axboe@fb.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Christoph Hellwig <hch@lst.de>,
loberman@redhat.com, linux-block@vger.kernel.org
Subject: Re: [PATCH] block: add back plugging in __blkdev_direct_IO
Date: Thu, 22 Dec 2016 11:31:02 -0700 [thread overview]
Message-ID: <3dd795f7-dd94-a71b-e797-8f0a0a655e33@fb.com> (raw)
In-Reply-To: <20161222182912.GA22997@infradead.org>
On 12/22/2016 11:29 AM, Christoph Hellwig wrote:
> On Thu, Dec 22, 2016 at 11:22:25AM -0700, Jens Axboe wrote:
>> On 12/22/2016 11:20 AM, Christoph Hellwig wrote:
>>> This allows sending larger than 1 MB requess to devices that support
>>> large I/O sizes.
>>
>> Thanks, I'll queue it up for this series.
>
> btw, s/requess/request/ above as just pointed out off-list.
I fixed it up.
--
Jens Axboe
prev parent reply other threads:[~2016-12-22 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 18:20 [PATCH] block: add back plugging in __blkdev_direct_IO Christoph Hellwig
2016-12-22 18:22 ` Jens Axboe
2016-12-22 18:29 ` Christoph Hellwig
2016-12-22 18:31 ` Jens Axboe [this message]
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=3dd795f7-dd94-a71b-e797-8f0a0a655e33@fb.com \
--to=axboe@fb.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=loberman@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox