From: Ming Lei <ming.lei@redhat.com>
To: Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: Hannes Reinecke <hare@suse.de>,
lsf-pc@lists.linux-foundation.org, linux-block@vger.kernel.org,
Xiaoguang Wang <xiaoguang.wang@linux.alibaba.com>,
linux-mm@kvack.org
Subject: Re: [LSF/MM/BPF TOPIC] block drivers in user space
Date: Wed, 30 Mar 2022 09:55:56 +0800 [thread overview]
Message-ID: <YkO4rFBHCdjCJndV@T590> (raw)
In-Reply-To: <87bkxor7ye.fsf@collabora.com>
On Tue, Mar 29, 2022 at 01:20:57PM -0400, Gabriel Krisman Bertazi wrote:
> Ming Lei <ming.lei@redhat.com> writes:
>
> >> I was thinking of something like this, or having a way for the server to
> >> only operate on the fds and do splice/sendfile. But, I don't know if it
> >> would be useful for many use cases. We also want to be able to send the
> >> data to userspace, for instance, for userspace networking.
> >
> > I understand the big point is that how to pass the io data to ubd driver's
> > request/bio pages. But splice/sendfile just transfers data between two FDs,
> > then how can the block request/bio's pages get filled with expected data?
> > Can you explain a bit in detail?
>
> Hi Ming,
>
> My idea was to split the control and dataplanes in different file
> descriptors.
>
> A queue has a fd that is mapped to a shared memory area where the
> request descriptors are. Submission/completion are done by read/writing
> the index of the request on the shared memory area.
>
> For the data plane, each request descriptor in the queue has an
> associated file descriptor to be used for data transfer, which is
> preallocated at queue creation time. I'm mapping the bio linearly, from
> offset 0, on these descriptors on .queue_rq(). Userspace operates on
> these data file descriptors with regular RW syscalls, direct splice to
> another fd or pipe, or mmap it to move data around. The data is
> available on that fd until IO is completed through the queue fd. After
> an operation is completed, the fds are reused for the next IO on that
> queue position.
>
> Hannes has pointed out the issues with fd limits. :)
OK, thanks for the detailed explanation!
Also you may switch to map each request queue/disk into a FD, and every
request is mapped to one fixed extent of the 'file' via rq->tag since we
have max sectors limit for each request, then fd limits can be avoided.
But I am wondering if this way is friendly to userspace side implementation,
since there isn't buffer, only FDs visible to userspace.
thanks,
Ming
next prev parent reply other threads:[~2022-03-30 1:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87tucsf0sr.fsf@collabora.com>
[not found] ` <986caf55-65d1-0755-383b-73834ec04967@suse.de>
2022-03-27 16:35 ` [LSF/MM/BPF TOPIC] block drivers in user space 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 [this message]
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
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=YkO4rFBHCdjCJndV@T590 \
--to=ming.lei@redhat.com \
--cc=hare@suse.de \
--cc=krisman@collabora.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=xiaoguang.wang@linux.alibaba.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).