From: longli@linuxonhyperv.com
To: Stephen Hemminger <stephen@networkplumber.org>,
Wei Hu <weh@microsoft.com>, Thomas Monjalon <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, Long Li <longli@microsoft.com>
Subject: [Patch v2] doc: announce bus/vmbus API changes
Date: Fri, 14 Mar 2025 17:34:55 -0700 [thread overview]
Message-ID: <1741998895-31065-1-git-send-email-longli@linuxonhyperv.com> (raw)
From: Long Li <longli@microsoft.com>
All vmbus APIs are used internally by DPDK core and net/netvsc PMD.
It's not feasible or practical to use those APIs by the application.
Those APIs will be moved from "DPDK" to "Internal" in DPDK 25.11.
Signed-off-by: Long Li <longli@microsoft.com>
---
Change in v2:
add details on what APIs will be changed
doc/guides/rel_notes/deprecation.rst | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 3f5f0e949c..0ff7dd69cd 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -138,3 +138,27 @@ Deprecation Notices
will be deprecated and subsequently removed in DPDK 24.11 release.
Before this, the new port library API (functions rte_swx_port_*)
will gradually transition from experimental to stable status.
+
+* bus/vmbus: Starting DPDK 25.11, all the vmbus APIs will be moved
+ from "DPDK" to "INTERNAL" in drivers/bus/vmbus/version.map.
+ Those APIs are used only by DPDK core and net/netvsc PMD.
+ The following APIs wil be moved:
+ rte_vmbus_chan_close
+ rte_vmbus_chan_open
+ rte_vmbus_chan_recv
+ rte_vmbus_chan_recv_raw
+ rte_vmbus_chan_rx_empty
+ rte_vmbus_chan_send
+ rte_vmbus_chan_send_sglist
+ rte_vmbus_chan_signal_read
+ rte_vmbus_chan_signal_tx
+ rte_vmbus_irq_mask
+ rte_vmbus_irq_read
+ rte_vmbus_irq_unmask
+ rte_vmbus_map_device
+ rte_vmbus_max_channels
+ rte_vmbus_probe
+ rte_vmbus_scan
+ rte_vmbus_set_latency
+ rte_vmbus_sub_channel_index
+ rte_vmbus_subchan_open
--
2.34.1
reply other threads:[~2025-03-15 0:35 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=1741998895-31065-1-git-send-email-longli@linuxonhyperv.com \
--to=longli@linuxonhyperv.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=longli@microsoft.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--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).