All of lore.kernel.org
 help / color / mirror / Atom feed
From: longli@linuxonhyperv.com
To: Stephen Hemminger <stephen@networkplumber.org>,
	Wei Hu <weh@microsoft.com>
Cc: dev@dpdk.org,
	root
	<root@longli-arm1-vm1.lxficwa3xisuzeoisceafmmd3f.cdmx.internal.cloudapp.net>
Subject: [Patch v3 0/6] Support VMBUS channels without monitoring enabled
Date: Fri,  4 Apr 2025 17:35:32 -0700	[thread overview]
Message-ID: <1743813338-28238-1-git-send-email-longli@linuxonhyperv.com> (raw)

From: root <root@longli-arm1-vm1.lxficwa3xisuzeoisceafmmd3f.cdmx.internal.cloudapp.net>

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. Becuase 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/

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

Change log:
v3: Add in the comment on the VMBUS API deprecation notice

 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-04-05  0:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-05  0:35 longli [this message]
2025-04-05  0:35 ` [Patch v3 1/6] net/netvsc: introduce private data for storing vmbus device for secondary process longli
2025-04-05  0:35 ` [Patch v3 2/6] net/netvsc: introduce get_vmbus_device to get the vmbus device longli
2025-04-05  0:35 ` [Patch v3 3/6] bus/vmbus: store UIO fd for secondary process longli
2025-04-05  0:35 ` [Patch v3 4/6] bus/vmbus: support channels without monitoring enabled longli
2025-04-05  0:35 ` [Patch v3 5/6] bus/vmbus: add rte_vmbus_device to all functions accessing vmbus longli
2025-04-05  0:35 ` [Patch v3 6/6] bus/vmbus: set event for channel without monitoring support longli
2025-04-06 16:08   ` Stephen Hemminger
2025-04-07 22:17     ` [EXTERNAL] " Long Li
2025-04-10 18:09     ` Long Li
2025-04-16 20:59       ` Long Li
2025-04-06 16:09 ` [Patch v3 0/6] Support VMBUS channels without monitoring enabled Stephen Hemminger

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=1743813338-28238-1-git-send-email-longli@linuxonhyperv.com \
    --to=longli@linuxonhyperv.com \
    --cc=dev@dpdk.org \
    --cc=root@longli-arm1-vm1.lxficwa3xisuzeoisceafmmd3f.cdmx.internal.cloudapp.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.