From: longli@linuxonhyperv.com
To: Stephen Hemminger <stephen@networkplumber.org>,
Wei Hu <weh@microsoft.com>
Cc: dev@dpdk.org, Long Li <longli@microsoft.com>
Subject: [PATCH 0/6] Support VMBUS channels without monitoring enabled
Date: Thu, 27 Feb 2025 17:08:17 -0800 [thread overview]
Message-ID: <1740704904-1493-1-git-send-email-longli@linuxonhyperv.com> (raw)
From: Long Li <longli@microsoft.com>
Hyperv may expose VMBUS channels without monitoring enabled. In this case,
it programs almost all the data traffic to VF.
This patchset enabled vmbus/netvsc to use channels without monitoring
enabled.
Long Li (6):
net/netvsc: introduce private data for storing vmbus device for
secondary process
net/netvsc: introduce get_vmbus_device to get the vmbus device
bus/vmbus: store UIO fd for secondary process
bus/vmbus: support channels without monitoring enabled
bus/vmbus: add rte_vmbus_device to all functions accessing vmbus
bus/vmbus: set event for channel without monitoring support
drivers/bus/vmbus/linux/vmbus_bus.c | 9 +++--
drivers/bus/vmbus/linux/vmbus_uio.c | 6 ++--
drivers/bus/vmbus/private.h | 2 +-
drivers/bus/vmbus/rte_bus_vmbus.h | 16 ++++++---
drivers/bus/vmbus/vmbus_channel.c | 52 ++++++++++++++++++++--------
drivers/bus/vmbus/vmbus_common_uio.c | 9 +++--
drivers/net/netvsc/hn_ethdev.c | 44 ++++++++++++++++++-----
drivers/net/netvsc/hn_nvs.c | 33 +++++++++++++-----
drivers/net/netvsc/hn_nvs.h | 21 +++++++----
drivers/net/netvsc/hn_rndis.c | 11 +++---
drivers/net/netvsc/hn_rxtx.c | 16 ++++-----
11 files changed, 152 insertions(+), 67 deletions(-)
--
2.34.1
reply other threads:[~2025-02-28 1:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1740704904-1493-1-git-send-email-longli@linuxonhyperv.com \
--to=longli@linuxonhyperv.com \
--cc=dev@dpdk.org \
--cc=longli@microsoft.com \
--cc=stephen@networkplumber.org \
--cc=weh@microsoft.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).