All of lore.kernel.org
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvmet: Use direct IO for writes
Date: Thu, 22 Sep 2016 15:57:07 +0200	[thread overview]
Message-ID: <20160922135707.GA14645@lst.de> (raw)
In-Reply-To: <1474481450-5036-1-git-send-email-sagi@grimberg.me>

On Wed, Sep 21, 2016@11:10:50AM -0700, Sagi Grimberg wrote:
> We're designed to work with high-end devices where
> direct IO makes perfect sense. We noticed that we
> context switch by scheduling kblockd instead of going
> directly to the device without REQ_SYNC for writes.

This looks reasonable.  But I still wonder why we bother to inject delay
for any fast blk-mq device (background: Sagi told me he is observing
issues without this on a NVMe PCIe card backend)

  reply	other threads:[~2016-09-22 13:57 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 [this message]
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

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=20160922135707.GA14645@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 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.