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 AAA82A0542; Mon, 24 Oct 2022 17:28:01 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9B5F3427F0; Mon, 24 Oct 2022 17:28:01 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by mails.dpdk.org (Postfix) with ESMTP id 6266C40A8B for ; Mon, 24 Oct 2022 17:28:00 +0200 (CEST) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 1DD125C00C8; Mon, 24 Oct 2022 11:28:00 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Mon, 24 Oct 2022 11:28:00 -0400 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=fm3; t=1666625280; x= 1666711680; bh=dqMtlZWXAl6vAOcZReFhH7Wd0+bZVWlBxRAnjZdB3/4=; b=z TnSsZET6y60h7tgcWLX12yDdtCOM8vxRF3sdToNGMnaAEB6dMXMUL2b1xOiZmOT5 8KKVbAQETm0wiInggBZeKzRxyL/b+/+5bKCposB1ITh2l83tHVtaLm4UrC+lTFje oqhgmtU59m/ISxdW3rcQaMiD7NXC0RP5k/jCAAyyz0ZR0PS3sRl+QhKYAooS7ZZU ThatiX3uFxPH/8cHHgIa5z7HkUrgQ1N8Qx2YXj8kbfKhE4zJL7cZmZgI2tmyjHT8 3tBarN5yCw6d1F457zqngks8FcBB6KXQprzTsbvGnXaX3kj7iBB/NzlsACk2NZVV 9qYq607P5cKSBD9r79rHw== 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=fm3; t=1666625280; x= 1666711680; bh=dqMtlZWXAl6vAOcZReFhH7Wd0+bZVWlBxRAnjZdB3/4=; b=W whAjrs09Gt4+o2cwX5/C/38RDKvKWvO90Z1WOwWgWlxN/AyvA2OOrRi3khyKr8ar 3TkfJi/4KQi/0IpR0RGIoa/wExRnANk26P4YTvt+FEyhVbEBPJ30MzoEvPMspJ2M EdWAd9pK54p6HqTiLB9uXJWpgUdnya353OQ4+BhFoI4o87syHxTaa9cwwnOeFJh8 +38LvEx0osafkA1IJCVIb1jXYdY+jOULIj6N+karTYkfftyxvdZzT9bvo0uyn6to 0pv0szR62Jid5DWrwl7QmuHKFk3HTyxz5mLzXMt++VsaK5BFPinSoZIl3ViqrIO9 Nmeb/ayfCzGv1OzDGOjCQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrgedtgedgkeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 24 Oct 2022 11:27:59 -0400 (EDT) From: Thomas Monjalon To: Sean Zhang Cc: Matan Azrad , Viacheslav Ovsiienko , dev@dpdk.org Subject: Re: [v3] net/mlx5: add port representor item support Date: Mon, 24 Oct 2022 17:27:58 +0200 Message-ID: <4776853.31r3eYUQgx@thomas> In-Reply-To: <20221024014815.10598-1-xiazhang@nvidia.com> References: <20221020012028.250527-1-xiazhang@nvidia.com> <20221024014815.10598-1-xiazhang@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 As title, I suggest: net/mlx5: support matching flow on port representor ID 24/10/2022 03:48, Sean Zhang: > Add support for port_representor item, it will match on traffic > originated from representor port specified in the pattern. This item > is supported in FDB steering domain only (in the flow with transfer > attribute). > > For example, below flow will redirect the destination of traffic from > ethdev 1 to ethdev 2. > > testpmd> ... pattern eth / port_representor port_id is 1 / end actions > represented_port ethdev_port_id 2 / ... > > To handle abovementioned item, Tx queue matching is added in the driver, > and the flow will be expanded to number of the Tx queues. If the spec of > port_representor is NULL, the flow will not be expanded and match on > traffic from any representor port. > > Signed-off-by: Sean Zhang > Acked-by: Viacheslav Ovsiienko