From: axboe@kernel.dk (Jens Axboe)
Subject: [PATCH] nvmet: Use direct IO for writes
Date: Fri, 23 Sep 2016 15:13:58 -0600 [thread overview]
Message-ID: <509f0edb-4208-5fbb-e706-ea9a49d4c9af@kernel.dk> (raw)
In-Reply-To: <766d06e4-748f-e380-c522-5977794c66ac@grimberg.me>
On 09/23/2016 03:12 PM, Sagi Grimberg wrote:
>
>>> So are we OK with bypassing that in nvmet?
>>
>> I'm OK with the patch as posted.
>
> Thanks, I'll queue it up for 4.9
You can add my Reviewed-by, fwiw.
--
Jens Axboe
next prev parent reply other threads:[~2016-09-23 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 18:10 [PATCH] nvmet: Use direct IO for writes Sagi Grimberg
2016-09-22 13:57 ` Christoph Hellwig
2016-09-22 14:09 ` Jens Axboe
2016-09-23 21:00 ` Sagi Grimberg
2016-09-23 21:01 ` Jens Axboe
2016-09-23 21:12 ` Sagi Grimberg
2016-09-23 21:13 ` Jens Axboe [this message]
2016-09-23 23:36 ` 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=509f0edb-4208-5fbb-e706-ea9a49d4c9af@kernel.dk \
--to=axboe@kernel.dk \
/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.