From: Sagi Grimberg <sagi@grimberg.me>
To: Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Hannes Reinecke <hare@suse.de>,
Bart Van Assche <bvanassche@acm.org>,
Mike Christie <michael.christie@oracle.com>,
lsf-pc@lists.linux-foundation.org, linux-block@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] block drivers in user space
Date: Thu, 24 Mar 2022 19:05:48 +0200 [thread overview]
Message-ID: <692ef2af-240e-9682-5530-5d55e49797d5@grimberg.me> (raw)
In-Reply-To: <87bkxwqwvn.fsf@collabora.com>
>>> FYI, I have absolutely no interest in supporting any userspace hooks
>>> in nvmet.
>>
>> Don't think we are discussing adding anything specific to nvmet, a
>> userspace backend will most likely sit behind a block device exported
>> via nvmet (at least from my perspective). Although I do see issues
>> with using the passthru interface...
>>
>>> If you want a userspace nvme implementation please use SPDK.
>>
>> The original use-case did not include nvmet, I may have stirred
>> the pot saying that we have nvmet loopback instead of a new kind
>> of device with a new set of tools.
>>
>> I don't think that spdk meets even the original android use-case.
>>
>> Not touching nvmet is fine, it just eliminates some of the possible
>> use-cases. Although personally I don't see a huge issue with adding
>> yet another backend to nvmet...
>
> After discussing with google for the r/w/flush use-case (cloud, not
> android), they are interested in avoiding the source of complexity that
> arises from implementing the NVMe protocol in the interface. Even if it
> is hidden behind a userspace library, it means converting block
> rq->nvme->block rq, which might have a performance impact?
>
> From your previous message, I think we can move forward with dissociating
> the original use case from nvme passthrough, and have the userspace hook
> as a block driver?
Yes, there is no desire to do that.
next prev parent reply other threads:[~2022-03-24 17:05 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 19:59 [LSF/MM/BPF TOPIC] block drivers in user space Gabriel Krisman Bertazi
2022-02-21 23:16 ` Damien Le Moal
2022-02-21 23:30 ` Gabriel Krisman Bertazi
2022-02-22 6:57 ` Hannes Reinecke
2022-02-22 14:46 ` Sagi Grimberg
2022-02-22 17:46 ` Hannes Reinecke
2022-02-22 18:05 ` Gabriel Krisman Bertazi
2022-02-24 9:37 ` Xiaoguang Wang
2022-02-24 10:12 ` Sagi Grimberg
2022-03-01 23:24 ` Khazhy Kumykov
2022-03-02 16:16 ` Mike Christie
2022-03-13 21:15 ` Sagi Grimberg
2022-03-14 17:12 ` Mike Christie
2022-03-15 8:03 ` Sagi Grimberg
2022-03-14 19:21 ` Bart Van Assche
2022-03-15 6:52 ` Hannes Reinecke
2022-03-15 8:08 ` Sagi Grimberg
2022-03-15 8:12 ` Christoph Hellwig
2022-03-15 8:38 ` Sagi Grimberg
2022-03-15 8:42 ` Christoph Hellwig
2022-03-23 19:42 ` Gabriel Krisman Bertazi
2022-03-24 17:05 ` Sagi Grimberg [this message]
2022-03-15 8:04 ` Sagi Grimberg
2022-02-22 18:05 ` Bart Van Assche
2022-03-02 23:04 ` Gabriel Krisman Bertazi
2022-03-03 7:17 ` Hannes Reinecke
2022-03-27 16:35 ` Ming Lei
2022-03-28 5:47 ` Kanchan Joshi
2022-03-28 5:48 ` Hannes Reinecke
2022-03-28 20:20 ` Gabriel Krisman Bertazi
2022-03-29 0:30 ` Ming Lei
2022-03-29 17:20 ` Gabriel Krisman Bertazi
2022-03-30 1:55 ` Ming Lei
2022-03-30 18:22 ` Gabriel Krisman Bertazi
2022-03-31 1:38 ` Ming Lei
2022-03-31 3:49 ` Bart Van Assche
2022-04-08 6:52 ` Xiaoguang Wang
2022-04-08 7:44 ` Ming Lei
2022-02-23 5:57 ` Gao Xiang
2022-02-23 7:46 ` Damien Le Moal
2022-02-23 8:11 ` Gao Xiang
2022-02-23 22:40 ` Damien Le Moal
2022-02-24 0:58 ` Gao Xiang
2022-06-09 2:01 ` Ming Lei
2022-06-09 2:28 ` Gao Xiang
2022-06-09 4:06 ` Ming Lei
2022-06-09 4:55 ` Gao Xiang
2022-06-10 1:52 ` Ming Lei
2022-07-28 8:23 ` Pavel Machek
2022-03-02 16:52 ` Mike Christie
2022-03-03 7:09 ` Hannes Reinecke
2022-03-14 17:04 ` Mike Christie
2022-03-15 6:45 ` Hannes Reinecke
2022-03-05 7:29 ` Dongsheng Yang
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=692ef2af-240e-9682-5530-5d55e49797d5@grimberg.me \
--to=sagi@grimberg.me \
--cc=bvanassche@acm.org \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=krisman@collabora.com \
--cc=linux-block@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=michael.christie@oracle.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;
as well as URLs for NNTP newsgroup(s).