From: <jerinj@marvell.com>
To: <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>
Cc: <stable@dpdk.org>, Nikhil Rao <nikhil.rao@intel.com>
Subject: [dpdk-stable] [dpdk-dev] [PATCH v2] eventdev: fix doxygen comment
Date: Tue, 2 Jul 2019 12:15:48 +0530 [thread overview]
Message-ID: <20190702064548.48265-1-jerinj@marvell.com> (raw)
In-Reply-To: <20190619080309.32188-1-jerinj@marvell.com>
From: Jerin Jacob <jerinj@marvell.com>
Update rte_eventdev.h file description to adapt to Tx adapter changes.
Fixes: c9bf83947e2e ("eventdev: add eth Tx adapter APIs")
Cc: stable@dpdk.org
Cc: Nikhil Rao <nikhil.rao@intel.com>
Signed-off-by: Jerin Jacob <jerinj@marvell.com>
---
v2:
- Removed refference to rte_event_eth_tx_adapter_enqueue() API and made
generic Tx adapter API to address RTE_EVENT_ETH_TX_ADAPTER_CAP_INTERNAL_PORT
vs non RTE_EVENT_ETH_TX_ADAPTER_CAP_INTERNAL_PORT case(Nikhil)
---
lib/librte_eventdev/rte_eventdev.h | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/lib/librte_eventdev/rte_eventdev.h b/lib/librte_eventdev/rte_eventdev.h
index 517cd8083..927f43c24 100644
--- a/lib/librte_eventdev/rte_eventdev.h
+++ b/lib/librte_eventdev/rte_eventdev.h
@@ -181,9 +181,8 @@
* The *dequeue* operation gets one or more events from the event ports.
* The application process the events and send to downstream event queue through
* rte_event_enqueue_burst() if it is an intermediate stage of event processing,
- * on the final stage, the application may send to different subsystem like
- * ethdev to send the packet/event on the wire using ethdev
- * rte_eth_tx_burst() API.
+ * on the final stage, the application may use Tx adapter API for maintaining
+ * the ingress order and then send the packet/event on the wire.
*
* The point at which events are scheduled to ports depends on the device.
* For hardware devices, scheduling occurs asynchronously without any software
--
2.21.0
next prev parent reply other threads:[~2019-07-02 6:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 8:03 [dpdk-stable] [dpdk-dev] [PATCH] " jerinj
2019-06-24 6:13 ` Rao, Nikhil
2019-07-02 6:45 ` jerinj [this message]
2019-07-02 7:35 ` [dpdk-stable] [dpdk-dev] [PATCH v2] " Rao, Nikhil
2019-07-02 7:44 ` Jerin Jacob Kollanukkaran
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=20190702064548.48265-1-jerinj@marvell.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=nikhil.rao@intel.com \
--cc=stable@dpdk.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).