From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 64AEEA0547 for ; Wed, 29 Sep 2021 12:02:04 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DCF39410D7; Wed, 29 Sep 2021 12:02:03 +0200 (CEST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id 9B13C40E3C for ; Wed, 29 Sep 2021 12:02:02 +0200 (CEST) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 41E565C00F5; Wed, 29 Sep 2021 06:02:02 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Wed, 29 Sep 2021 06:02:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm2; bh= pc0mHzgdBM1o5l9TfFLuZAlum173kPgyb44UJMEYPu0=; b=LiTYI0rqn7KBM+ad a4ZxXqhzB2PDeKcuc3YG+cSvnjfTNCDGu4vI7bz5VDnKAwrQZw5RDmrG0umxnn8h ZWwW/ICeIebF9UhqZjhq8wHVZSLJPgp4QDH9T8+8fK9kwzUHLLD8L5DPeOAw5O7Y tkbmqoSa4x1RllGiNSjEooCczPOeIBdgAzomNGKoK3lGtP/MqJ9EAynopp+2WZn7 RQrMN/x5zSuvlfDedjKDpn68KuQpjhnihqfLvYUr1IzYFNOy+BpqD4mCWhyLzF2Y k2R5RFPSgHdrubidKLlhrBlM3IdqQkiMdzFiE7fpnWzBe9+xsZORWdxNf+EKm5s9 ROI3/Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=pc0mHzgdBM1o5l9TfFLuZAlum173kPgyb44UJMEYP u0=; b=nPs5KxmeNQvWss6ESiOwuDju3/2TxB/FS0kED1hVwoVHtoTJufKzsXHKv 0Biqje5HqUi525oEeSAsU1NL3Z+PfW8KT/lREo4+bUqN5a1r3QnyDyt8wiKUvDFx lN7p7zotodYVp8XI3Oe8o4fxRFojq6+gAt1J8FT8ChhB8z1gT01Y1hIeD/DbgjfI HAnjdJUB5/+OaVTldA5Bj69L+uLqscOGX30Z47/f38Wf6Dy7oxl7ryTepio/UV9t SFgLOvdrzSzTcds9MjFkbBT8yItf7ToDr/NNM/fAkIoFdCwa9D+FtEkr9j9+pyjh 0TfIN9vHL02AnupDbKIdlIHoi/ReA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudekvddgvddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepffdvffejueetleefieeludduuefgteejleevfeekjeefieegheet ffdvkeefgedunecuffhomhgrihhnpeguphgukhdrohhrghenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhn rdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 29 Sep 2021 06:02:01 -0400 (EDT) From: Thomas Monjalon To: Jaeeun Ham Cc: "users@dpdk.org" , jerinj@marvell.com, jay.jayatheerthan@intel.com Subject: Re: [dpdk-users] TX/RX adapter running on the same core problem Date: Wed, 29 Sep 2021 12:02:00 +0200 Message-ID: <1955512.eRcRny8Yuf@thomas> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org +Cc eventdev maintainers 26/09/2021 07:21, Jaeeun Ham: > Hi, > > I hope you are well. > > During the traffic test, TX adapter showed starvation due to Rx adapter processing on the same dpdk-core 03 and dropped the 41412 packets after 154655 tx_retry. > So, I expect I have to assign TX/RX adapter on each dpdk-core to prevent starvation and packet drop. > > Are those tx_retry and tx_dropped packet due to RX adapter packet processing? > Is it possible to separate TX/RX adapter into different dpdk-core? > > ========[ TX adapter stats ]======== > tx_retry: 154655 > tx_packets: 438771 > tx_dropped: 41412 > > > < eventdev_dump.txt > > ========[ Services ]======== > qdispatch_service_id : 0 > txa_service_id : 1 > rxa_service_id : 2 > edk_service_id : 3 > timer_service_id : 4 > timer_adapter_service_id: 5 > > Service Cores Summary > dpdk-core 01: PDCP Fastpath Plugin control function thread > > dpdk-core qu-dispat txadapter rxadapter edk tmr tmr-adapt > 03 0 770574949 770574948 0 0 0 > 05 816421027 0 0 816421571 816421571 816421571 > 07 896307282 0 0 896307828 896307828 0 > 09 899213296 0 0 899213687 899213687 0 > 11 889323680 0 0 889323871 889323871 0 > 13 897300534 0 0 897300686 897300686 0 > 15 891124716 0 0 891124811 891124811 0 > 17 896336177 0 0 896336212 896336211 0 > 19 895461845 0 0 895461846 895461846 0 > > ========[ Event dev port 0 ~ 10 xstats ]======== > - packet flow: f1u -> s1u one way > midhaul_ker -> midhaul_edk -> backhaul_edk -> backhaul_ker > port 09 Rx adapter -> port 07 -> port 06 -> port 08 -> port 09 Tx adapter > > port 00: dpdk-core 05, worker_core // queue-dispatcher, edk, timer > port 01: dpdk-core 07, worker_core // queue-dispatcher, edk, timer > port 02: dpdk-core 09, worker_core // queue-dispatcher, edk, timer > port 03: dpdk-core 11, worker_core // queue-dispatcher, edk, timer > port 04: dpdk-core 13, worker_core // queue-dispatcher, edk, timer > port 05: dpdk-core 15, worker_core // queue-dispatcher, edk, timer > port 06: dpdk-core 17, worker_core // queue-dispatcher, edk, timer > port 07: dpdk-core 19, worker_core // queue-dispatcher, edk, timer > port 08: TX adapter, dpdk-core 03 // packet transmission > port 09: RX adapter, dpdk-core 03 // packet receiving > port 10: Event timer adapter // tmr-adapter > > BR/Jaeeun > -------------- next part -------------- > An embedded and charset-unspecified text was scrubbed... > Name: eventdev_dump.txt > URL: >