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 C0CA9A0542; Mon, 24 Oct 2022 17:26:29 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 762F6427F0; Mon, 24 Oct 2022 17:26:29 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by mails.dpdk.org (Postfix) with ESMTP id C2FA340A8B for ; Mon, 24 Oct 2022 17:26:27 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 419725C00F1; Mon, 24 Oct 2022 11:26:24 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Mon, 24 Oct 2022 11:26:24 -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=1666625184; x= 1666711584; bh=mheYni86DvfMvFuSzVg4bV5grtp/fq4uJbXRGjWLBhE=; b=o Sa+HolSvcfXicjUECX5+mLp5UC9RzEs3bHrwwt1tT3vySUwlG7A+5XMOZsT3Mv0e TL1Mcvc1Fo8PIfx5dJNnFGj9rPfT3RBoRwwPCBfD+/E5yOPXw0OszhHwDn83cYmr WWU9uevhG47hY3VFdykxufh5j8nonBHUEoWBfl/gn2QPNXVCVnkMWtjGavrRLO0E 9riUD/ujqqxC1NY622peFJ0Jkv7F+VGWEEkIBsHD0OGHDc6xTgBLfwfRkdpD1zkc lwNHbHTWB+15caJa2CXb7KIDNxzw9xBSUOBjRoPXhOAbGvfh+RHNS/wh/F4osmGL vTEJ8GsQWxqPElI/U1tYA== 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=1666625184; x= 1666711584; bh=mheYni86DvfMvFuSzVg4bV5grtp/fq4uJbXRGjWLBhE=; b=t 5xzl4Ub9UZCJzSLujxlQx5kYovvza6MD10akYPVonnfjAl2kibLLCOajLPSkv84G ZnnoC0yHcoWyd4Yao8Vyo6wEcqpqIdPBOymm/qeGvSM3cKEdfDC14dsO89LbTvg/ ro+cx3yMkzR6/ux/AU3rsNnnr4rAw7gAlojtn8Umo0VwTbRM3MmiV2bEsfVr2wOI fEvhhbq6yfhdUSlX6grSZyARaKC++ftIRTunZW9gg4gPJ4N3uK7MsUtglHCfsAK7 ttZLZC90amsbX/bdSQSS4psNBSWcmLr8fLP/S52fUfCXuz1SmcQncF0ViYwbuRqZ s4QGD1NzMp833hH7wNxEw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrgedtgedgkeegucetufdoteggodetrfdotf 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:26:23 -0400 (EDT) From: Thomas Monjalon To: Sean Zhang Cc: Matan Azrad , Viacheslav Ovsiienko , dev@dpdk.org Subject: Re: [PATCH] net/mlx5: add port representor support Date: Mon, 24 Oct 2022 17:26:22 +0200 Message-ID: <5612955.DvuYhMxLoT@thomas> In-Reply-To: <20221019145734.147211-1-xiazhang@nvidia.com> References: <20221019145734.147211-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 The title is confusing. Port representor is already supported in mlx5. It seems you are adding support for matching on port representor ID, right? 19/10/2022 16:57, 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 > port 1 to port 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