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 C755D41CB3; Thu, 16 Feb 2023 18:42:07 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1D8B842D8F; Thu, 16 Feb 2023 18:42:07 +0100 (CET) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mails.dpdk.org (Postfix) with ESMTP id A3E2C40EE3 for ; Thu, 16 Feb 2023 18:42:05 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id DDF415C01E5; Thu, 16 Feb 2023 12:42:03 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Thu, 16 Feb 2023 12:42: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=1676569323; x= 1676655723; bh=unZkOX/Exv+vKYuOyw3NoPb74XBq6v2pKKiCyUVv6g0=; b=Z JtLmeK4tq09x9hVo4IwZ2YnE0Mu0S83gSPEdhNRvT7ly0OEKys6ARYJUxK60+q2R lfxlP8kfs4c3XYrMLWUm842M3hKMCAyPDmzAuCFGVykW5x3Q4qL0zgApEch+eDDN XzqMDS9ecSAQEUuuN0p4WGVjNLnZM4w+SK3YpP32GzymGeyxt2nnI6fkyLarsCkm 5li+xBKvlqK/RNe9BTldDq8X9U8Rd/16DmWm+d7OoH+vLVvsIiUM9pvJfJWarnff C1pf7TaAVNTJKCiHMoafKSogU2J0mFj2M2o9K3aIyqxyhLcPf1s02jwNss16wPkA I+DMmYN+vDRFrhhLur+CA== 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=1676569323; x= 1676655723; bh=unZkOX/Exv+vKYuOyw3NoPb74XBq6v2pKKiCyUVv6g0=; b=A rJBiCZKi4c3iQOVTxGrxC8JLU5xPhJlpJC0FPXF4VfZlrOcLDqdUkJi8rwqJo4Qf MSrZ2LR9Caa9Z7sYEue7z+P8hTysXi1GFz9LC1ziL9hgsFIFxRnHqfYuOXako4Hg fsp02M1Jw+dyn+jG5NxRr3pp4VMFvLeoXtDhuyIfTLEuGVLbUrSMwRVrThK9egZU YcUJga6Tt/uwHJ/fm8Z33d6rKTzunpAe0M1sWJccyAtedxGlLo3sKBvKzTEig5mJ dI8afZeRja+SwrBchVKCpDe2Z1iwBHNjveUDVfNeuuRpi8jfNyw8obKMTxz60EIE PoOVIgfzEd4xIxovF/LOw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudeijedguddtudcutefuodetggdotefrod 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:42: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 1/2] ethdev: introduce the Tx map API for aggregated ports Date: Thu, 16 Feb 2023 18:42:00 +0100 Message-ID: <1879381.g5d078U9FE@thomas> In-Reply-To: <20230214154836.9681-2-jiaweiw@nvidia.com> References: <20230203050717.46914-1-jiaweiw@nvidia.com> <20230214154836.9681-1-jiaweiw@nvidia.com> <20230214154836.9681-2-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 Tx queue mapping of aggregated ports 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 use for Tx via a queue. > > This patch introduces the new ethdev API > rte_eth_dev_map_aggr_tx_affinity(), it's used to map a Tx queue > with an aggregated port of the DPDK port (specified with port_id), > The affinity is the number of the aggregated port. > Value 0 means no affinity and traffic could be routed to any > aggregated port, this is the default current behavior. > > The maximum number of affinity is given by rte_eth_dev_count_aggr_ports(). > > Add the trace point for ethdev rte_eth_dev_count_aggr_ports() > and rte_eth_dev_map_aggr_tx_affinity() functions. > > Add the testpmd command line: > testpmd> port config (port_id) txq (queue_id) affinity (value) > > For example, there're two physical ports connected to > a single DPDK port (port id 0), and affinity 1 stood for > the first physical port and affinity 2 stood for the second > physical port. > Use the below commands to config tx phy affinity for per Tx Queue: > port config 0 txq 0 affinity 1 > port config 0 txq 1 affinity 1 > port config 0 txq 2 affinity 2 > port config 0 txq 3 affinity 2 > > These commands config the Tx Queue index 0 and Tx Queue index 1 with > phy affinity 1, uses Tx Queue 0 or Tx Queue 1 send packets, > these packets will be sent from the first physical port, and similar > with the second physical port if sending packets with Tx Queue 2 > or Tx Queue 3. > > Signed-off-by: Jiawei Wang Acked-by: Thomas Monjalon