From: Naga Harish K S V <s.v.naga.harish.k@intel.com>
To: jay.jayatheerthan@intel.com, jerinj@marvell.com
Cc: dev@dpdk.org
Subject: [PATCH 3/3] doc: added eth Tx adapter queue start stop APIs
Date: Thu, 8 Sep 2022 22:42:19 -0500 [thread overview]
Message-ID: <20220909034219.4018966-3-s.v.naga.harish.k@intel.com> (raw)
In-Reply-To: <20220909034219.4018966-1-s.v.naga.harish.k@intel.com>
Added tx adapter queue start - rte_event_eth_rx_adapter_queue_start()
and tx adapter queue stop - rte_event_eth_tx_adapter_queue_stop()
Signed-off-by: Naga Harish K S V <s.v.naga.harish.k@intel.com>
---
doc/guides/rel_notes/release_22_11.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/guides/rel_notes/release_22_11.rst b/doc/guides/rel_notes/release_22_11.rst
index c32c18ff49..dc1060660c 100644
--- a/doc/guides/rel_notes/release_22_11.rst
+++ b/doc/guides/rel_notes/release_22_11.rst
@@ -29,6 +29,10 @@ New Features
ethernet device id and Rx queue index.
Added ``rte_event_eth_tx_adapter_instance_get`` to get the Tx adapter instance id for specified
ethernet device id and Tx queue index.
+ Added ``rte_event_eth_tx_adapter_queue_start`` to start enqueueing packets to the Tx queue by
+ Tx adapter.
+ Added ``rte_event_eth_tx_adapter_queue_start`` to stop the Tx Adapter from transmitting any
+ mbufs to the Tx_queue.
.. This section should contain new features added in this release.
Sample format:
--
2.25.1
next prev parent reply other threads:[~2022-09-09 3:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 3:42 [PATCH 1/3] eventdev/eth_tx: add queue start stop API Naga Harish K S V
2022-09-09 3:42 ` [PATCH 2/3] test/eth_tx: add testcase for queue start stop APIs Naga Harish K S V
2022-09-09 3:42 ` Naga Harish K S V [this message]
2022-09-14 15:20 ` [PATCH 1/3] eventdev/eth_tx: add queue start stop API Jerin Jacob
2022-09-16 5:21 ` Naga Harish K, S V
2022-09-16 6:10 ` Jayatheerthan, Jay
2022-09-16 15:18 ` Naga Harish K, S V
2022-09-15 9:53 ` [PATCH v2 1/2] " Naga Harish K S V
2022-09-15 9:53 ` [PATCH v2 2/2] test/eth_tx: add testcase for queue start stop APIs Naga Harish K S V
2022-09-15 15:19 ` [PATCH v3 1/2] eventdev/eth_tx: add queue start stop API Naga Harish K S V
2022-09-15 15:19 ` [PATCH v3 2/2] test/eth_tx: add testcase for queue start stop APIs Naga Harish K S V
2022-09-16 15:15 ` [PATCH v4 1/2] eventdev/eth_tx: add queue start stop API Naga Harish K S V
2022-09-16 15:15 ` [PATCH v4 2/2] test/eth_tx: add testcase for queue start stop APIs Naga Harish K S V
2022-09-16 16:23 ` [PATCH v5 1/2] eventdev/eth_tx: add queue start stop API Naga Harish K S V
2022-09-16 16:23 ` [PATCH v5 2/2] test/eth_tx: add testcase for queue start stop APIs Naga Harish K S V
2022-09-26 2:04 ` [PATCH v6 1/2] eventdev/eth_tx: add queue start stop API Naga Harish K S V
2022-09-26 2:04 ` [PATCH v6 2/2] test/eth_tx: add testcase for queue start stop APIs Naga Harish K S V
2022-09-27 10:15 ` [PATCH v6 1/2] eventdev/eth_tx: add queue start stop API Jerin Jacob
2022-09-27 10:28 ` Jayatheerthan, Jay
2022-09-28 3:46 ` Jerin Jacob
-- strict thread matches above, loose matches on Subject: below --
2022-09-08 17:12 [PATCH 1/3] " Naga Harish K S V
2022-09-08 17:12 ` [PATCH 3/3] doc: added eth Tx adapter queue start stop APIs Naga Harish K S V
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=20220909034219.4018966-3-s.v.naga.harish.k@intel.com \
--to=s.v.naga.harish.k@intel.com \
--cc=dev@dpdk.org \
--cc=jay.jayatheerthan@intel.com \
--cc=jerinj@marvell.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).