From: Cindy Lu <lulu@redhat.com>
To: lulu@redhat.com, jasowang@redhat.com, mst@redhat.com,
maxime.coquelin@redhat.com, xieyongji@bytedance.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org
Subject: [RFC 0/4] reconnect support in vduse
Date: Wed, 28 Jun 2023 14:59:15 +0800 [thread overview]
Message-ID: <20230628065919.54042-1-lulu@redhat.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 653 bytes --]
Hi all
Here is the reconnect support in vduse, The steps
is map the pages from kernel to userland, usespace
app will wirte the vq_info in the pages
And then sync this information in kernel/user-space
I just the split mode, So only use the last_avail_idx
here, Will send the patch for DPDK later
Tested in vduse + dpdk test-pmd
Cindy Lu (4):
vduse: Add the struct to save the vq reconnect info
vduse: Add file operation for mmap
vduse: Add the function for get/free the mapp pages
vduse: update the vq_info in ioctl
drivers/vdpa/vdpa_user/vduse_dev.c | 107 +++++++++++++++++++++++++++++
1 file changed, 107 insertions(+)
--
2.34.3
next reply other threads:[~2023-06-28 8:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 6:59 Cindy Lu [this message]
2023-06-28 6:59 ` [RFC 1/4] vduse: Add the struct to save the vq reconnect info Cindy Lu
2023-06-28 8:03 ` Jason Wang
2023-07-01 9:24 ` Cindy Lu
2023-07-03 6:25 ` Jason Wang
2023-07-11 14:16 ` Maxime Coquelin
2023-06-28 6:59 ` [RFC 2/4] vduse: Add file operation for mmap Cindy Lu
2023-06-28 8:08 ` Jason Wang
2023-07-01 9:23 ` Cindy Lu
2023-07-11 14:18 ` Maxime Coquelin
2023-06-28 6:59 ` [RFC 3/4] vduse: Add the function for get/free the mapp pages Cindy Lu
2023-06-28 8:11 ` Jason Wang
2023-07-01 9:16 ` Cindy Lu
2023-06-28 6:59 ` [RFC 4/4] vduse: update the vq_info in ioctl Cindy Lu
2023-06-28 8:13 ` Jason Wang
2023-07-01 9:14 ` Cindy Lu
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=20230628065919.54042-1-lulu@redhat.com \
--to=lulu@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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
all inboxes | Powered by JetHome®