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 4308541CB3; Thu, 16 Feb 2023 18:46:06 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C7F7942D65; Thu, 16 Feb 2023 18:46:05 +0100 (CET) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mails.dpdk.org (Postfix) with ESMTP id 2F4B842D1A for ; Thu, 16 Feb 2023 18:46:04 +0100 (CET) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id B90DC5C01CF; Thu, 16 Feb 2023 12:46:03 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 16 Feb 2023 12:46:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm1; t=1676569563; x= 1676655963; bh=wWCsjL4lUDJjaaUlBIlo3s3vsX0EhA80bcoUGpMd5bs=; b=X XYSmlV0AN9+RAZRFGQOSGkmQ3oejHiEZaqDKCrbBq/qBSa/FhzP+5TB5DpSyeZyQ 2ADM+18Jjjai14AGOHmzL3eegEoQJgsrTVIokR8YjIlNwK2k0aJ7rLpn9HXcz0xa e6J0CJOS0U/Zd4Mfhg28sIl/PA2rD4GivN/aHRlKJ3KmuD52ES6LzuJMZNNKbHij 1yYue2gwlBWrrY+yFP1Qsj7czKbH8FBFcvWjDTr9L9tu15eir6ErX7gzELyyZw5s Ycu2bZmUQjc0aRxr0qJTUB1u6aIQeb3Au28JDJJ17t0so15UHHON/CrG+HsnhnSV uyAVQpthDekPI7wEbe8Gg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1676569563; x= 1676655963; bh=wWCsjL4lUDJjaaUlBIlo3s3vsX0EhA80bcoUGpMd5bs=; b=T im10vFmpn87iSbj0O2N3DOe6na+QuQVLtw3TKBhxcUHFE2cSNMcQvoHzIASooPqf hLt25lvlxJqEgWYevrZuEUsGJV0GhzPTvCH/MG9hWdIkMcCXV4uQtXv7N081E/GQ xOErB/1m0T/I1vcjUauZH0LWecpOkft5jDoE6O3Tbb6a7XoZO/SpXwWxOmwVrZER 63ovz/BFIIQE2bo57QkqC9nz0EPoeUXjYVEFfAv5vXDRiqIUfNdKkF3TVrslzdP+ 1sWCxHquEsHOSmti44Ak5e2BlPjUNVFsQs8TxIW0OyT7daYWn+deo1955lVpwx4q oEAAAAacvWK0D7VZg3KSw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudeijedguddtvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvfevufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhho mhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqne cuggftrfgrthhtvghrnheptdejieeifeehtdffgfdvleetueeffeehueejgfeuteeftddt ieekgfekudehtdfgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 16 Feb 2023 12:46:02 -0500 (EST) From: Thomas Monjalon To: Jiawei Wang Cc: viacheslavo@nvidia.com, orika@nvidia.com, andrew.rybchenko@oktetlabs.ru, Aman Singh , Yuying Zhang , Ferruh Yigit , dev@dpdk.org, rasland@nvidia.com Subject: Re: [PATCH v5 2/2] ethdev: add Aggregated affinity match item Date: Thu, 16 Feb 2023 18:46:01 +0100 Message-ID: <2892561.2VHbPRQshP@thomas> In-Reply-To: <20230214154836.9681-3-jiaweiw@nvidia.com> References: <20230203050717.46914-1-jiaweiw@nvidia.com> <20230214154836.9681-1-jiaweiw@nvidia.com> <20230214154836.9681-3-jiaweiw@nvidia.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org For the title, I suggest ethdev: add flow matching of aggregated port 14/02/2023 16:48, Jiawei Wang: > When multiple ports are aggregated into a single DPDK port, > (example: Linux bonding, DPDK bonding, failsafe, etc.), > we want to know which port is used for Rx and Tx. > > This patch allows to map a Rx queue with an aggregated port by using > a flow rule. The new item is called RTE_FLOW_ITEM_TYPE_AGGR_AFFINITY. > > While uses the aggregated affinity as a matching item in the flow rule, > and sets the same affinity value by call > rte_eth_dev_map_aggr_tx_affinity(), then the packet can be sent from > the same port as the receiving one. > The affinity numbering starts from 1, then trying to match on > aggr_affinity 0 will result in an error. > > Add the testpmd command line to match the new item: > flow create 0 ingress group 0 pattern aggr_affinity affinity is 1 / > end actions queue index 0 / end > > The above command means that creates a flow on a single DPDK port and > matches the packet from the first physical port and redirects > these packets into Rx queue 0. > > Signed-off-by: Jiawei Wang Acked-by: Thomas Monjalon