From: axboe@fb.com (Jens Axboe)
Subject: [PATCH/RFC] NVMe: add support for doing offline/online of attached namespaces
Date: Fri, 23 Jan 2015 10:24:45 -0700 [thread overview]
Message-ID: <54C283DD.8080809@fb.com> (raw)
In-Reply-To: <20150123171112.GA2650@infradead.org>
On 01/23/2015 10:11 AM, Christoph Hellwig wrote:
> On Fri, Jan 23, 2015@08:24:30AM -0700, Jens Axboe wrote:
>> This is an RFC patch. The goal is as listed, being able to detach any
>> namespaces and bdevs from a device, so we just have the admin part left.
>> I'm open to alternative suggestions on how to handle this. Solutions
>> that include rmmod/modprobe if the driver wont work if you have more
>> than one NVMe device in a system.
>
> Aways use the scsi to nvme translation and run the thing through the
> SCSI layer where all these issues are already handled? I'm only half
> joking, with features like multipathing and reservations coming up
> this actually does seem like the best long term direction once we've
> cut the remaining fat from the SCSI I/O path.
It'd be an interesting experiment in seeing how close scsi-mq is to raw
performance, I'd be worried there's still quite a gap though. Maybe when
we're further along it starts to become a more viable option, at least I
would not rule it out.
At the same time, this is a feature we use/need now. So I don't think a
potential switch in future direction should preclude that from being
done now.
--
Jens Axboe
next prev parent reply other threads:[~2015-01-23 17:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 15:24 [PATCH/RFC] NVMe: add support for doing offline/online of attached namespaces Jens Axboe
2015-01-23 17:11 ` Christoph Hellwig
2015-01-23 17:24 ` Jens Axboe [this message]
2015-01-23 17:31 ` Christoph Hellwig
2015-01-23 17:39 ` Jens Axboe
2015-01-23 17:44 ` Christoph Hellwig
2015-01-23 17:46 ` Jens Axboe
2015-01-23 17:51 ` Christoph Hellwig
2015-01-23 17:52 ` Jens Axboe
2015-01-27 20:59 ` Keith Busch
2015-01-28 16:13 ` 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=54C283DD.8080809@fb.com \
--to=axboe@fb.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