From: Stephen Hemminger <stephen@networkplumber.org>
To: longli@linuxonhyperv.com
Cc: Wei Hu <weh@microsoft.com>, dev@dpdk.org, Long Li <longli@microsoft.com>
Subject: Re: [patch v6 0/6] Support VMBUS channels without monitoring enabled
Date: Thu, 17 Apr 2025 09:34:42 -0700 [thread overview]
Message-ID: <20250417093442.743b3daa@hermes.local> (raw)
In-Reply-To: <1744837038-5387-1-git-send-email-longli@linuxonhyperv.com>
On Wed, 16 Apr 2025 13:57:12 -0700
longli@linuxonhyperv.com wrote:
> 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.
>
> This needs to change the APIs exposed by drivers/bus/vmbus. Because those
> APIs are used only by NetVSC PMD and not feasible for use by a DPDK
> application, all VMBUS APIs are set to deprecate in upcoming 25.11 release.
>
> The notice for deprecation is accepted in the following patch:
> https://patchwork.dpdk.org/project/dpdk/patch/1742242184-19600-1-git-send-email-longli@linuxonhyperv.com/
>
> Change log:
> v3: Add in the comment on the VMBUS API deprecation notice
>
> 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 | 53 ++++++++++++++++++++--------
> 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, 153 insertions(+), 67 deletions(-)
>
Applied to next-net with some minor shortening of commit subjects to appease
check-git-log.sh
prev parent reply other threads:[~2025-04-17 16:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 20:57 longli
2025-04-16 20:57 ` [patch v6 1/6] net/netvsc: introduce private data for storing vmbus device for secondary process longli
2025-04-16 20:57 ` [patch v6 2/6] net/netvsc: introduce get_vmbus_device to get the vmbus device longli
2025-04-16 20:57 ` [patch v6 3/6] bus/vmbus: store UIO fd for secondary process longli
2025-04-16 20:57 ` [patch v6 4/6] bus/vmbus: support channels without monitoring enabled longli
2025-04-16 20:57 ` [patch v6 5/6] bus/vmbus: add rte_vmbus_device to all functions accessing vmbus longli
2025-04-16 20:57 ` [patch v6 6/6] bus/vmbus: set event for channel without monitoring support longli
2025-04-17 16:34 ` Stephen Hemminger [this message]
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=20250417093442.743b3daa@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=longli@linuxonhyperv.com \
--cc=longli@microsoft.com \
--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).