From: Jason Wang <jasowang@redhat.com>
To: Xie Yongji <xieyongji@bytedance.com>,
mst@redhat.com, stefanha@redhat.com, sgarzare@redhat.com,
parav@nvidia.com, bob.liu@oracle.com, hch@infradead.org,
rdunlap@infradead.org, willy@infradead.org,
viro@zeniv.linux.org.uk, axboe@kernel.dk, bcrl@kvack.org,
corbet@lwn.net
Cc: linux-aio@kvack.org, netdev@vger.kernel.org,
linux-fsdevel@vger.kernel.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [RFC v3 08/11] vduse: Introduce VDUSE - vDPA Device in Userspace
Date: Tue, 26 Jan 2021 16:19:25 +0800 [thread overview]
Message-ID: <1f419a24-cd53-bd73-5b8a-8ab5d976a490@redhat.com> (raw)
In-Reply-To: <20210119050756.600-2-xieyongji@bytedance.com>
On 2021/1/19 下午1:07, Xie Yongji wrote:
> This VDUSE driver enables implementing vDPA devices in userspace.
> Both control path and data path of vDPA devices will be able to
> be handled in userspace.
>
> In the control path, the VDUSE driver will make use of message
> mechnism to forward the config operation from vdpa bus driver
> to userspace. Userspace can use read()/write() to receive/reply
> those control messages.
>
> In the data path, VDUSE_IOTLB_GET_FD ioctl will be used to get
> the file descriptors referring to vDPA device's iova regions. Then
> userspace can use mmap() to access those iova regions. Besides,
> the eventfd mechanism is used to trigger interrupt callbacks and
> receive virtqueue kicks in userspace.
>
> Signed-off-by: Xie Yongji<xieyongji@bytedance.com>
> ---
> Documentation/driver-api/vduse.rst | 85 ++
> Documentation/userspace-api/ioctl/ioctl-number.rst | 1 +
> drivers/vdpa/Kconfig | 7 +
> drivers/vdpa/Makefile | 1 +
> drivers/vdpa/vdpa_user/Makefile | 5 +
> drivers/vdpa/vdpa_user/eventfd.c | 221 ++++
> drivers/vdpa/vdpa_user/eventfd.h | 48 +
> drivers/vdpa/vdpa_user/iova_domain.c | 426 +++++++
> drivers/vdpa/vdpa_user/iova_domain.h | 68 ++
> drivers/vdpa/vdpa_user/vduse.h | 62 +
> drivers/vdpa/vdpa_user/vduse_dev.c | 1217 ++++++++++++++++++++
> include/uapi/linux/vdpa.h | 1 +
> include/uapi/linux/vduse.h | 125 ++
> 13 files changed, 2267 insertions(+)
> create mode 100644 Documentation/driver-api/vduse.rst
> create mode 100644 drivers/vdpa/vdpa_user/Makefile
> create mode 100644 drivers/vdpa/vdpa_user/eventfd.c
> create mode 100644 drivers/vdpa/vdpa_user/eventfd.h
> create mode 100644 drivers/vdpa/vdpa_user/iova_domain.c
> create mode 100644 drivers/vdpa/vdpa_user/iova_domain.h
> create mode 100644 drivers/vdpa/vdpa_user/vduse.h
> create mode 100644 drivers/vdpa/vdpa_user/vduse_dev.c
> create mode 100644 include/uapi/linux/vduse.h
Btw, if you could split this into three parts:
1) iova domain
2) vduse device
3) doc
It would be more easier for the reviewers.
Thanks
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-01-26 8:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210119045920.447-1-xieyongji@bytedance.com>
[not found] ` <20210119045920.447-5-xieyongji@bytedance.com>
2021-01-20 3:44 ` [RFC v3 04/11] vhost-vdpa: protect concurrent access to vhost device iotlb Jason Wang
[not found] ` <20210119045920.447-2-xieyongji@bytedance.com>
2021-01-20 4:24 ` [RFC v3 01/11] eventfd: track eventfd_signal() recursion depth separately in different cases Jason Wang
[not found] ` <CACycT3sN0+dg-NubAK+N-DWf3UDXwWh=RyRX-qC9fwdg3QaLWA@mail.gmail.com>
2021-01-27 3:37 ` Jason Wang
[not found] ` <CACycT3sqDgccOfNcY_FNcHDqJ2DeMbigdFuHYm9DxWWMjkL7CQ@mail.gmail.com>
2021-01-28 3:04 ` Jason Wang
2021-01-28 3:08 ` Jens Axboe
[not found] ` <CACycT3u6Ayf_X8Mv4EvF+B=B4OzFSK8ygvJMRnO6CDgYF13Qnw@mail.gmail.com>
2021-01-28 4:31 ` Jason Wang
[not found] ` <20210119045920.447-6-xieyongji@bytedance.com>
2021-01-20 5:55 ` [RFC v3 05/11] vdpa: shared virtual addressing support Jason Wang
[not found] ` <CACycT3vXCaSc9Er3yzRAzf8-eEFgpQYmEaDy3129xPdb4AFdmA@mail.gmail.com>
2021-01-27 3:43 ` Jason Wang
[not found] ` <20210119045920.447-7-xieyongji@bytedance.com>
2021-01-20 6:24 ` [RFC v3 06/11] vhost-vdpa: Add an opaque pointer for vhost IOTLB Jason Wang
[not found] ` <CACycT3voF9x4o95XtLtkKF-i261JXMMsYR1PgssYFwg15jZXQA@mail.gmail.com>
2021-01-27 3:51 ` Jason Wang
[not found] ` <20210119050756.600-1-xieyongji@bytedance.com>
[not found] ` <20210119050756.600-2-xieyongji@bytedance.com>
2021-01-19 14:53 ` [RFC v3 08/11] vduse: Introduce VDUSE - vDPA Device in Userspace Jonathan Corbet
2021-01-19 17:53 ` Randy Dunlap
2021-01-26 8:08 ` Jason Wang
[not found] ` <CACycT3uJtKqEp7CHBKhvmSL41gTrCcMrt_-tacGCbX1nabuG6w@mail.gmail.com>
2021-01-28 4:27 ` Jason Wang
[not found] ` <CACycT3upvTrkm5Cd6KzphSk=FYDjAVCbFJ0CLmha5sP_h=5KGg@mail.gmail.com>
2021-01-28 6:14 ` Jason Wang
2021-01-26 8:19 ` Jason Wang [this message]
[not found] ` <20210119050756.600-4-xieyongji@bytedance.com>
2021-01-26 8:09 ` [RFC v3 10/11] vduse: grab the module's references until there is no vduse device Jason Wang
[not found] ` <20210119050756.600-5-xieyongji@bytedance.com>
2021-01-26 8:17 ` [RFC v3 11/11] vduse: Introduce a workqueue for irq injection Jason Wang
[not found] ` <20210119045920.447-4-xieyongji@bytedance.com>
2021-01-20 3:46 ` [RFC v3 03/11] vdpa: Remove the restriction that only supports virtio-net devices Jason Wang
2021-01-20 11:08 ` Stefano Garzarella
2021-01-27 3:33 ` Jason Wang
2021-01-27 8:57 ` Stefano Garzarella
2021-01-28 3:11 ` Jason Wang
2021-01-29 15:03 ` Stefano Garzarella
[not found] ` <CACycT3sTx+NGg1iB8gmFbOPfzCvnq5F0nd2ePGs2_BUeU=-2_Q@mail.gmail.com>
2021-02-01 11:05 ` Stefano Garzarella
2021-01-27 8:59 ` Stefano Garzarella
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=1f419a24-cd53-bd73-5b8a-8ab5d976a490@redhat.com \
--to=jasowang@redhat.com \
--cc=axboe@kernel.dk \
--cc=bcrl@kvack.org \
--cc=bob.liu@oracle.com \
--cc=corbet@lwn.net \
--cc=hch@infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=rdunlap@infradead.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=virtualization@lists.linux-foundation.org \
--cc=willy@infradead.org \
--cc=xieyongji@bytedance.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).