From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 97E6941B9D;
	Wed,  1 Feb 2023 11:12:35 +0100 (CET)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 323974021F;
	Wed,  1 Feb 2023 11:12:35 +0100 (CET)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com
 [66.111.4.29]) by mails.dpdk.org (Postfix) with ESMTP id D6A5140141
 for <dev@dpdk.org>; Wed,  1 Feb 2023 11:12:33 +0100 (CET)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id 5ED7E5C006D;
 Wed,  1 Feb 2023 05:12:33 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163])
 by compute1.internal (MEProxy); Wed, 01 Feb 2023 05:12:33 -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=1675246353; x=
 1675332753; bh=JcV0txs14qvYLNIxV3Eu2tFBdeeE3IvlfqprWWzPp4g=; b=t
 bmxBTXBpxAz88k3HaQcHBXaA8dOcSVjdypoD6Hl75rBi0d6smeZDM3hzbEKpkmNS
 jtx8SSl0NO49ULGxs8keoQBqzycVRSeEpUANdU6aXlzmqKHSi7gol3+IiLWdW7S1
 EJrG8+oy8OzOinUqy94s2gQ6ilDL6HbecL/pzvw517jwKHjUlVylX1oN6troqSIz
 FtKjaOzJiO6hkKKTWkv0i0t82DG6yBl/P5qr9a+Fxxfoax1Jws+1hohicD5PQ8XI
 LRc41z2hBiROtnTpqFY4SvvaIfxGdFTTywbivRifwZLAXKLzyhHeTNADJA5r/lW1
 uQpUCHlGivaf3C9Nhekgw==
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=1675246353; x=
 1675332753; bh=JcV0txs14qvYLNIxV3Eu2tFBdeeE3IvlfqprWWzPp4g=; b=o
 eAF0XaEuKV4nGjN6R1RP1kYTBri8VJqbnoxWAaeB6s4sYTXVSYQOEo5828mX6eG0
 IzSNQhKOBXDI5tMleLm5UCh1zH/MiF9GSbxpgKjgDZBovIgeLWLva12zz7GAuNMv
 s+nNji1YSwFOuQVSFyXaPODPtoct1abinwRTIBpHiepVVJgEXhrHv1eDfKzjeeUh
 5j9VNBd7wy9ray78xQCud+ne2RPay0u0HHCcPR6fuPm14MNxBWtUsukBrj0f4aIZ
 0cIP6OjafIUhINXcao9MeCooQwq7ZRCR4KBsKxM/u87vRUiNtpaU5wOH8knldqn7
 oPD4oRfmXaTy8cyts6/eA==
X-ME-Sender: <xms:ETvaY06ZyYe8tbunXNXPn2VwrTDtf-7BeK5i2aeTtBuxndVhO9lwyg>
 <xme:ETvaY152cDC3IDuxCLSYuukUswQDGxnca2tunTMbtbIcfSOViqUCT-pMOx3xhCNMC
 H6SJFEZJfpSeIEubA>
X-ME-Received: <xmr:ETvaYzcyQ0TfSR3Wiuz8LDY8YvIyZCoHxyIYO-R0Eg_rInBfWEEgpEbTAt-M2-pvO8zlxqboqwEJM2dJ2LKSyAUu5A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudefiedgudefucetufdoteggodetrfdotf
 fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
 uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne
 cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm
 rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc
 ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei
 kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh
 hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght
X-ME-Proxy: <xmx:ETvaY5I3UbHz6z2cWtNcgX634w_EJRW1Cb14WDiIbUNr3P52fswAWA>
 <xmx:ETvaY4KZXYqpt73wkhXjGyxRE4Mip78oOCPdN0oB0ib7zAwqjGBYAA>
 <xmx:ETvaY6zEg8KH5Za-Dd1EJmX9MWxzf2JeZQfhHL5ygaalkFXn_mBXRw>
 <xmx:ETvaY9VgS7MfeUPsLvOIM_nfORs1RCaA_7cNjKuhcRICF-qgG-30BA>
Feedback-ID: i47234305:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed,
 1 Feb 2023 05:12:31 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: Rongwei Liu <rongweil@nvidia.com>, Ivan Malov <ivan.malov@arknetworks.am>
Cc: Matan Azrad <matan@nvidia.com>, Slava Ovsiienko <viacheslavo@nvidia.com>, 
 Ori Kam <orika@nvidia.com>, Aman Singh <aman.deep.singh@intel.com>,
 Yuying Zhang <yuying.zhang@intel.com>, Ferruh Yigit <ferruh.yigit@amd.com>,
 Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
 "dev@dpdk.org" <dev@dpdk.org>, Raslan Darawsheh <rasland@nvidia.com>
Subject: Re: [PATCH v7] ethdev: add special flags when creating async transfer
 table
Date: Wed, 01 Feb 2023 11:12:30 +0100
Message-ID: <1707507.QkHrqEjB74@thomas>
In-Reply-To: <d3a0acc3-513-2b36-03-52430327c5a@arknetworks.am>
References: <20221114115946.1074787-1-rongweil@nvidia.com>
 <BN9PR12MB5273268248D41EBF5A9E7D10ABD09@BN9PR12MB5273.namprd12.prod.outlook.com>
 <d3a0acc3-513-2b36-03-52430327c5a@arknetworks.am>
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 <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org

31/01/2023 06:30, Ivan Malov:
> Hi Rongwei,
> 
> OK, I hear ya. Thanks for persevering.
> 
> I still hope community will comment on the possibility to
> provide a hint mechanism for always-the-same match items,
> with the perspective of becoming more versatile.

Any hint could be imagined.
But please keep this in mind: a hint is *not* a matching criteria,
for the simple reason that a hint can be ignored by the PMD.
So you cannot use a hint to avoid specifying a match item,
but you could use a hint to specify that an item is the same
for all the rules of a table.


> Other
> than that, your current patch might be OK, but, again,
> I think other reviewers' comments (if any) shall
> be addressed. But no strong objections from me.
> 
> By the way, for this "specialise" field, in your opinion,
> which extra flags could emerge in future / would be nice
> to have? I mean, is there any concept of what can be
> added to this field's namespace and what can't be?

I think there is no limit with hint flags to be added.
I repeat it again: hints can be ignored by the PMDs.