From: Vamsi Attunuru <vattunuru@marvell.com>
To: <fengchengwen@huawei.com>, <dev@dpdk.org>,
<kevin.laatz@intel.com>, <bruce.richardson@intel.com>
Cc: <jerinj@marvell.com>, <anoobj@marvell.com>,
Vamsi Attunuru <vattunuru@marvell.com>
Subject: [PATCH] doc: announce dmadev new capability addition
Date: Mon, 29 Jul 2024 05:49:27 -0700 [thread overview]
Message-ID: <20240729124927.264458-1-vattunuru@marvell.com> (raw)
Announce addition of new capability flag and fields in
rte_dma_info and rte_dma_conf structures.
Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>
---
RFC:
https://patchwork.dpdk.org/project/dpdk/patch/20240729115558.263574-1-vattunuru@marvell.com/
doc/guides/rel_notes/deprecation.rst | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 6948641ff6..05d28473c0 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -147,3 +147,8 @@ 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.
+
+* dmadev: A new flag ``RTE_DMA_CAPA_QOS`` will be introduced to advertise
+ dma device's QoS capability. Also new fields will be added in ``rte_dma_info``
+ and ``rte_dma_conf`` structures to get device supported priority levels
+ and to configure the required priority level.
--
2.25.1
next reply other threads:[~2024-07-29 12:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 12:49 Vamsi Attunuru [this message]
2024-07-29 15:20 ` Jerin Jacob
2024-07-29 17:17 ` Morten Brørup
2024-07-31 10:24 ` Thomas Monjalon
2024-07-30 12:10 ` [PATCH v2] doc: announce changes to dma device structures Amit Prakash Shukla
2024-07-30 12:53 ` [PATCH v3] " Amit Prakash Shukla
2024-07-30 14:46 ` [PATCH v4] " Amit Prakash Shukla
2024-07-30 17:27 ` Jerin Jacob
2024-07-31 11:01 ` Thomas Monjalon
2024-07-31 16:06 ` Thomas Monjalon
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=20240729124927.264458-1-vattunuru@marvell.com \
--to=vattunuru@marvell.com \
--cc=anoobj@marvell.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=jerinj@marvell.com \
--cc=kevin.laatz@intel.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).