From: Wei Hu <weh@microsoft.com>
To: Long Li <longli@microsoft.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXTERNAL] [Patch v7 0/4] Support VMBUS channels without monitoring enabled
Date: Wed, 6 Aug 2025 16:02:52 +0000 [thread overview]
Message-ID: <OSQP153MB13078454F0A3C58013A86949BB2DA@OSQP153MB1307.APCP153.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <1753834183-22244-1-git-send-email-longli@linuxonhyperv.com>
> -----Original Message-----
> From: longli@linuxonhyperv.com <longli@linuxonhyperv.com>
> Sent: Wednesday, July 30, 2025 8:10 AM
> To: Stephen Hemminger <stephen@networkplumber.org>; Wei Hu
> <weh@microsoft.com>
> Cc: dev@dpdk.org; Long Li <longli@microsoft.com>
> Subject: [EXTERNAL] [Patch v7 0/4] Support VMBUS channels without
> monitoring enabled
>
> 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatc
> hwork.dpdk.org%2Fproject%2Fdpdk%2Fpatch%2F1742242184-19600-1-
> git-send-email-
> longli%40linuxonhyperv.com%2F&data=05%7C02%7Cweh%40microsoft.com
> %7C31b5d1d8465a4a7e2e7208ddcefd648b%7C72f988bf86f141af91ab2d7
> cd011db47%7C1%7C0%7C638894309981905236%7CUnknown%7CTWFpb
> GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4z
> MiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Ai4Y01e
> rExEqaHxj5NV9oo2gdDdh%2FELHRQusxShm2W4%3D&reserved=0
>
> Change log:
> v3: Add in the comment on the VMBUS API deprecation notice
> v7: Dropped the first two patches in the seires as they have already been
> applied to net-next
>
> Long Li (4):
> 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_nvs.c | 18 +++++-----
> drivers/net/netvsc/hn_nvs.h | 15 ++++----
> drivers/net/netvsc/hn_rndis.c | 11 +++---
> drivers/net/netvsc/hn_rxtx.c | 16 ++++-----
> 10 files changed, 97 insertions(+), 58 deletions(-)
>
> --
> 2.25.1
Reviewed-by: Wei Hu <weh@microsoft.com>
prev parent reply other threads:[~2025-08-06 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 0:09 longli
2025-07-30 0:09 ` [Patch v7 1/4] bus/vmbus: store UIO fd for secondary process longli
2025-07-30 0:09 ` [Patch v7 2/4] bus/vmbus: support channels without monitoring enabled longli
2025-07-30 0:09 ` [Patch v7 3/4] bus/vmbus: add rte_vmbus_device to all functions accessing vmbus longli
2025-07-30 0:09 ` [Patch v7 4/4] bus/vmbus: set event for channel without monitoring support longli
2025-08-06 16:02 ` Wei Hu [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=OSQP153MB13078454F0A3C58013A86949BB2DA@OSQP153MB1307.APCP153.PROD.OUTLOOK.COM \
--to=weh@microsoft.com \
--cc=dev@dpdk.org \
--cc=longli@microsoft.com \
--cc=stephen@networkplumber.org \
/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).