From patchwork Tue Jul 2 06:45:48 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jerin Jacob Kollanukkaran X-Patchwork-Id: 55852 X-Patchwork-Delegate: jerinj@marvell.com Return-Path: X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id E1E6758C6; Tue, 2 Jul 2019 08:46:15 +0200 (CEST) Received: from mx0b-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) by dpdk.org (Postfix) with ESMTP id C10CC4C8F; Tue, 2 Jul 2019 08:46:14 +0200 (CEST) Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x626jff8012823; Mon, 1 Jul 2019 23:46:13 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marvell.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type; s=pfpt0818; bh=LoE5wB0qH7DVQVMxSBspq0Dy0B212+05tVWoxJkwZBw=; b=HO9T9/CxE0dLLz/374I2qIkDvvCgrwH5ZSPKhiJUmjbR2Nm9+z98587k4XJFUcDdMCmD meDM+G39vVNR19+ZHyRoT/orfaOsh75SuKyZu9ATOaDkVwPVOE3eobzprijPnc9C3iq6 Q5ECihg1v4E+XxeMQ6a7eL4nV5PRrId1dUdxFeVnDLeSuwfiaAlqiU/jeWS54Wkax/aQ bOoI2MloDCw6H8jA3RaCmIA/m10eWRmZ1SWnEtBLatJUNi5DQQwgI7UALwtCpl5LF8+e e7kWp6IHuohg5gfdyLfqNxk/5BybwZ2WlPXgmtb+nVmyUjhBJa2mM5Rfv6jfyxhzHx8m XQ== Received: from sc-exch03.marvell.com ([199.233.58.183]) by mx0a-0016f401.pphosted.com with ESMTP id 2tfvk6s40d-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 01 Jul 2019 23:46:13 -0700 Received: from SC-EXCH03.marvell.com (10.93.176.83) by SC-EXCH03.marvell.com (10.93.176.83) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Mon, 1 Jul 2019 23:46:12 -0700 Received: from maili.marvell.com (10.93.176.43) by SC-EXCH03.marvell.com (10.93.176.83) with Microsoft SMTP Server id 15.0.1367.3 via Frontend Transport; Mon, 1 Jul 2019 23:46:12 -0700 Received: from jerin-lab.marvell.com (jerin-lab.marvell.com [10.28.34.14]) by maili.marvell.com (Postfix) with ESMTP id D94AE3F703F; Mon, 1 Jul 2019 23:46:10 -0700 (PDT) From: To: , Jerin Jacob CC: , Nikhil Rao Date: Tue, 2 Jul 2019 12:15:48 +0530 Message-ID: <20190702064548.48265-1-jerinj@marvell.com> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190619080309.32188-1-jerinj@marvell.com> References: <20190619080309.32188-1-jerinj@marvell.com> MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-07-02_03:, , signatures=0 Subject: [dpdk-dev] [PATCH v2] eventdev: fix doxygen comment X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" From: Jerin Jacob 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 Signed-off-by: Jerin Jacob Reviewed-by: Nikhil Rao --- 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