From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvmet: Use direct IO for writes
Date: Sat, 24 Sep 2016 01:36:00 +0200 [thread overview]
Message-ID: <20160923233600.GA19147@lst.de> (raw)
In-Reply-To: <766d06e4-748f-e380-c522-5977794c66ac@grimberg.me>
On Fri, Sep 23, 2016@02:12:38PM -0700, 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
Btw, it might be a good idea to send our for-4.9 branch to Jens
so it gets some linux-next exposure.
prev parent reply other threads:[~2016-09-23 23:36 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
2016-09-23 23:36 ` Christoph Hellwig [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=20160923233600.GA19147@lst.de \
--to=hch@lst.de \
/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).