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 0450F43B79 for ; Thu, 7 Mar 2024 09:43:33 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id F169840295; Thu, 7 Mar 2024 09:43:32 +0100 (CET) Received: from fhigh1-smtp.messagingengine.com (fhigh1-smtp.messagingengine.com [103.168.172.152]) by mails.dpdk.org (Postfix) with ESMTP id AB5F840272; Thu, 7 Mar 2024 09:43:30 +0100 (CET) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailfhigh.nyi.internal (Postfix) with ESMTP id 2117E11400B1; Thu, 7 Mar 2024 03:43:30 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Thu, 07 Mar 2024 03:43:30 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1709801010; x=1709887410; bh=JecAaa8s1ymHGqQdOFZ+8YwJrzAXvrcway/UOY10mnQ=; b= bgc1wjjuptmqYp7wsnGgV49TiATNnNJbqaFdTZEfsN218TxyKDup/zWWATJ2LDVc CEi+buJpKha0BH0ufAfMd23axY5tGOgMk5lsY4dDdICC5aN7dt3uLNOaTZwAzHrR JP/yAs0pNkkqH0ypOROmk07KhY7npPdFckGCD1oFJb2AcwTdBM+SoXo7QV5PJzqE ceQDrokjjEptUzbK5oh8Au/rsf+vjqzBCThYd6P7+45MmdK0rrEBd3WPPMj3jZZ+ 6zgYRWpRMPrQO4TawTgYLwbf+r8Qut+WnuKHIiLmWrgHs6r325sl/9IP06SCAN05 IfsTa8vqC4F4fs4phHyq+g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1709801010; x= 1709887410; bh=JecAaa8s1ymHGqQdOFZ+8YwJrzAXvrcway/UOY10mnQ=; b=O qYuULXgD9vQN4y0hUdwE/rhZM7ykd/rgA/hYNfjyWKqott2WWX+dzqFlI/M5rkRr rcgV6TncCuFM98NtlTaGsaYBWveEeYNhk+oXz3kD1YzgpfNa7xHlkY4rqVO1CS1k GdKpZvq5ZiL0aV1Gh2zZzUWZH1omjv9SFSajPNROdjNKDQyOJocnVD9vaAGJ3aoa omN5/OZMibpKOG+FhGZPjkxZecqI3yyqkEuvamb1DLE+0avAzPJokASetEs+12I2 yGu6sVloFuSM8l1eZvF0uxD1QLlgqido4iaFO+uTXd0lTcAnpPH7IFnYW56u3JzX EhyE38MXqp6vLlAGP3cHw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledriedvgdduvdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 7 Mar 2024 03:43:28 -0500 (EST) From: Thomas Monjalon To: Konstantin Ananyev , Konstantin Ananyev Cc: "dev@dpdk.org" , stable@dpdk.org, Jerin Jacob , Pavan Nikhilesh Bhagavatula Subject: Re: [EXTERNAL] [PATCH] examples/l3fwd: fix Rx over not ready port Date: Thu, 07 Mar 2024 09:43:27 +0100 Message-ID: <2122038.VsPgYW4pTa@thomas> In-Reply-To: References: <20240301163931.107036-1-konstantin.v.ananyev@yandex.ru> <8d7c91e9d91446a8b57d9d690e4a7ec3@huawei.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org > > > > Running l3fwd in event mode with SW eventdev, service cores > > > > can start RX before main thread is finished with PMD installation. > > > > to reproduce: > > > > ./dpdk-l3fwd --lcores=49,51 -n 6 -a ca:00.0 -s 0x8000000000000 \ > > > > --vdev event_sw0 -- \ > > > > -L -P -p 1 --mode eventdev --eventq-sched=ordered \ > > > > --rule_ipv4=test/l3fwd_lpm_v4_u1.cfg -- > > rule_ipv6=test/l3fwd_lpm_v6_u1.cfg > > > > \ > > > > --no-numa > > > > > > > > At init stage user will most likely see the error message like that: > > > > ETHDEV: lcore 51 called rx_pkt_burst for not ready port 0 > > > > 0: ./dpdk-l3fwd (rte_dump_stack+0x1f) [15de723] > > > > ... > > > > 9: ./dpdk-l3fwd (eal_thread_loop+0x5a2) [15c1324] > > > > ... > > > > > > > > And then all depends how luck/unlucky you are. > > > > If there are some actual packet in HW RX queue, then the app will most > > > > likely crash, otherwise it might survive. > > > > As error message suggests, the problem is that services are started > > > > before main thread finished with NIC setup and initialization. > > > > The suggested fix moves services startup after NIC setup phase. > > > > > > > > Bugzilla ID: 1390 > > > > Fixes: 8bd537e9c6cf ("examples/l3fwd: add service core setup based on > > > > caps") > > > > Cc: stable@dpdk.org > > > > > > > > Signed-off-by: Konstantin Ananyev > > > > Signed-off-by: Konstantin Ananyev > > Acked-by: Pavan Nikhilesh Applied, thanks.