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 4D8744249C; Fri, 27 Jan 2023 09:54:40 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E044940150; Fri, 27 Jan 2023 09:54:39 +0100 (CET) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by mails.dpdk.org (Postfix) with ESMTP id 44AFC40146 for ; Fri, 27 Jan 2023 09:54:39 +0100 (CET) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id C29E45C018F; Fri, 27 Jan 2023 03:54:38 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Fri, 27 Jan 2023 03:54:38 -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=fm3; t=1674809678; x= 1674896078; bh=WJP5NAKbaydsdXWmKwScL4GoA5Fmk8xtBd0NREXCoBM=; b=s lpG51JF723XFqlSlbuzpcxJG1FuDfJc2vAB8aIBfNMiPn+JsC6jDqutUm5e/7nId adeBBEZks1pOufJVp4IkxSyDf3wp4o/oWpq+4DONqst8n41uhOFcy3eFCnMRnbPD mGZBc3//3dP1Pj0/u6MHyM8hxluaQrt1dFPfrE09+1z7RD6qbCllLZhVvyUUQ5EC 4syLNU4bCfiGl4F1SQk8iarEcQ312P+2L/OJxoB6+uRW2D0hmjz74JpXZ2SjOx6/ /7zjWX19K6fc/Z5cMnp4KUnp57Z6MWftA58b6RLj/CHPyATq+azVfr4HENlBp1hn C0IILLlWAqzjiQFowp+ug== 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=1674809678; x= 1674896078; bh=WJP5NAKbaydsdXWmKwScL4GoA5Fmk8xtBd0NREXCoBM=; b=e LONcohqVz6IptHt5jFvEQOJj7hqcte/k+Oo0n0yHEhjajkWkIDTi/JVQHw9pJFvW FFQwFCicBjzNuVs2SV4+klowUCqYU1ZvC1vnaiJWzBuJxlrTlm+SQlDrTxozgMtd zbdYAVSzlKopYISVaE1i2k6CPLC6jPkycPDeLFMTE3FitXEA29iliubWksfIafZT mgBdJt+OPfJbEl1EK+ImT7Yt7bgc/PcL5FNZd7bm3ELUfePw9x3iCISx3QyKWa/I pLRx2CYT4D9DDB4jlK+04TZoO0MLga8Su8DeJTfEBhejIDMA6L3SlSRvrh5MSmwW C/adUXscX0aBvT+ZtlqNw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedruddvhedguddvjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvfevufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhho mhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqne cuggftrfgrthhtvghrnheptdejieeifeehtdffgfdvleetueeffeehueejgfeuteeftddt ieekgfekudehtdfgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 27 Jan 2023 03:54:36 -0500 (EST) From: Thomas Monjalon To: Nithin Kumar Dabilpuram Cc: Aman Singh , Yuying Zhang , Ivan Malov , Andrew Rybchenko , "dev@dpdk.org" , Hanumanth Reddy Pothula , Ferruh Yigit , "viacheslavo@nvidia.com" , Jerin Jacob Kollanukkaran , "david.marchand@redhat.com" Subject: Re: [EXT] Re: [PATCH v5 2/2] app/testpmd: add command to process Rx metadata negotiation Date: Fri, 27 Jan 2023 09:54:35 +0100 Message-ID: <4531200.rE2NhlSrgm@thomas> In-Reply-To: References: <20221220200250.2413443-1-hpothula@marvell.com> <2238537.U75o6juQT5@thomas> 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 27/01/2023 06:02, Nithin Kumar Dabilpuram: > From: Thomas Monjalon > > Ferruh is proposing to have a command "port config ..." > > to configure the flags to negotiate. > > Are you OK with this approach? > > Yes, we are fine to have such command to enable and disable the feature > with default being it disabled if supported by PMD. > Is default being disabled fine if the feature is supported by a PMD ? I think the default should be enabled for ease of use. Do we have similar features disables by default? I mean do we know features in testpmd which require a "double enablement" like one configuration command + one rte_flow rule?