From: axboe@kernel.dk (Jens Axboe)
Subject: [PATCH] NVMe: Add rw_page support
Date: Fri, 14 Nov 2014 08:07:49 -0700 [thread overview]
Message-ID: <54661AC5.7000605@kernel.dk> (raw)
In-Reply-To: <20141114145858.GF11522@wil.cx>
On 11/14/2014 07:58 AM, Matthew Wilcox wrote:
> On Thu, Nov 13, 2014@06:29:37PM -0700, Jens Axboe wrote:
>> The downside I see is that this is an OOB IO path. Once we start adding IO
>> scheduling for those that need that, then this will completely bypass that.
>
> The idea is that you would only enable it for devices that are based on
> NVM that is of "near-DRAM" speeds, and can complete small I/Os as fast
> as they are issued. For those kinds of devices, there is absolutely no
> value to any kind of IO scheduling.
I agree, that's not the kind of device that people would generally do
scheduling on, and we can't at those rates. But if that's the case, why
isn't this a sync interface? "Near DRAM speeds" and interrupt driven
seems like a poor choice.
--
Jens Axboe
next prev parent reply other threads:[~2014-11-14 15:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 0:05 [PATCH] NVMe: Add rw_page support Keith Busch
2014-11-14 1:29 ` Jens Axboe
2014-11-14 14:58 ` Matthew Wilcox
2014-11-14 15:07 ` Jens Axboe [this message]
2014-11-14 15:52 ` Matthew Wilcox
2014-11-14 16:32 ` Jens Axboe
2014-11-14 17:05 ` Keith Busch
2014-11-14 20:53 ` Jens Axboe
2014-11-14 22:59 ` Keith Busch
2014-11-14 14:55 ` Matthew Wilcox
[not found] ` <CANvN+ekQTdNgPe33iaM_9=2Hjrfds2B2R3d3XK06K9n=SY+ZKA@mail.gmail.com>
2014-11-14 22:50 ` Keith Busch
2014-11-14 22:56 ` Jens Axboe
2014-11-14 23:04 ` Keith Busch
2014-11-14 23:30 ` 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=54661AC5.7000605@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox