From: Hannes Reinecke <hare@suse.de>
To: Mike Christie <michael.christie@oracle.com>,
Gabriel Krisman Bertazi <krisman@collabora.com>,
lsf-pc@lists.linux-foundation.org
Cc: linux-block@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] block drivers in user space
Date: Thu, 3 Mar 2022 08:09:00 +0100 [thread overview]
Message-ID: <57af4fe0-9042-729a-18e9-839a5f0a84ac@suse.de> (raw)
In-Reply-To: <526a8360-d7d3-1211-087b-c86d5a68380b@oracle.com>
On 3/2/22 17:52, Mike Christie wrote:
> On 2/21/22 1:59 PM, Gabriel Krisman Bertazi wrote:
>> I'd like to discuss an interface to implement user space block devices,
>> while avoiding local network NBD solutions. There has been reiterated
>
> Besides the tcmu approach, I've also worked on the local nbd based
> solution like here:
>
> https://github.com/gluster/nbd-runner
>
> Have you looked into a modern take that uses io_uring's socket features
> with the zero copy work that's being worked on for it? If so, what are
> the issues you have hit with that? Was it mostly issues with the zero
> copy part of it?
>
>
Problem is that we'd need an _inverse_ io_uring interface.
The current io_uring interface writes submission queue elements,
and waits for completion queue elements.
For this use-case we'd need to convert it to wait for submission queue
elements, and write completion queue elements.
IE completely invert the operation.
Not sure if we can convert it _that_ easily ...
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
next prev parent reply other threads:[~2022-03-03 7:09 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
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 [this message]
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=57af4fe0-9042-729a-18e9-839a5f0a84ac@suse.de \
--to=hare@suse.de \
--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).