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 1437A41B9F; Wed, 1 Feb 2023 15:23:31 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BC5D24021D; Wed, 1 Feb 2023 15:23:30 +0100 (CET) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id 8A45340141 for <dev@dpdk.org>; Wed, 1 Feb 2023 15:23:29 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 40D825C00C6; Wed, 1 Feb 2023 09:23:26 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 01 Feb 2023 09:23:26 -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=1675261406; x= 1675347806; bh=dll9KAKh04nDT1AJea5B57vmKB881Z4ezGqNa8ToQv4=; b=d Esu3pj67CiwUqr+y9cOFV1I1hkSeNkr9/YLfhJ9S27f0rpvmpWtX0XxU1U8Dw+Jq fkVDEY1LRmyeHqyzO6KfSv85I6/UcCcimtVaBlmhMb4YNxV2hOQ0ajlXH0CQ0DyO tJ+vy/eTmB9XEKRq/fBTDh4ZGERfDfDBymsQwJESOIy6uIhmEUtY0EaqdEgaOy9O m5YeHo1qab7T70+k7NbJvwPQBDHpF20frJ5w1KzMi7nbmEqYwOnetD4xqNWcQcnN tMnNYruaD3SF9q7CqCdRib9Gev8oYfBYrrY3R663yVDe7/jWOA1CrV6fbT10rik8 nqXPEl2Za7PbNdUpyDQnw== 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=1675261406; x= 1675347806; bh=dll9KAKh04nDT1AJea5B57vmKB881Z4ezGqNa8ToQv4=; b=i XOY7aO+7HC2japsQ76WgBsEkeq49Y7C1IXh512HvybFqewYHESYud9ICNTquXfug NUY0suOgMk7oJWLP1ErIz1g249FwPloOX5tAJhCYsmxfiq25kxKZ74M7mQ7csN5T ZhdxBRuoNT0ZKvWbResQNsJGhm9iuwq7KJslnjRFmgd532XkBwVoq5f/lLxAPiam dNYHd6pQMQlVllQWcavkvkkoZVZUns+EEPK+hdPGrgNq2WZHR7z8L0QwR/1lVSFZ I9spv8ZRju2Llpou3BX0xWbOQ+EIboBzVdiNkM/Nonkaiafvki39ErIfv/Rhgs40 Cx835HIUO1vzGCcg/9E+Q== X-ME-Sender: <xms:3XXaYzczKkfq0mdvR5KwriAGTtBo5otFwXfrOf-AHz3rDiUCkbOa-A> <xme:3XXaY5NUpWcXvAR8YuXDO1ZOCMY7EZxXRwRcZxq07B8RacHq4eMOPmkM8u4Sk20Jn p8Q-VPh04GDisacwA> X-ME-Received: <xmr:3XXaY8hsRRQXRH7PqqmMuVPu5twyct69rux7ENDK7LkOhhnIY-UJmwLZ0E8F6qRGd_8pd3JcpJbhwPIMsXSuuD55iA> X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudefiedgieegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: <xmx:3XXaY09tjv7Urs3X2tQDJ7cJptO_56uPHL_5R9HWKDkRHaENiq5aGg> <xmx:3XXaY_tI8dvtBhSfClwC3t7IcKAEVdu3lwB3EsE_Rxtb7Ln61IZBnQ> <xmx:3XXaYzExmN-17LpifME-Nrgo5TTmR0EQgAuhCkhHHlAAagyGEbyjmQ> <xmx:3nXaY9J_5QPTTXm8oFAlgPNmgLG5PVTuh6eIG90TeLIiX4RxWM-szQ> Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 1 Feb 2023 09:23:24 -0500 (EST) From: Thomas Monjalon <thomas@monjalon.net> To: Ivan Malov <ivan.malov@arknetworks.am> Cc: Rongwei Liu <rongweil@nvidia.com>, 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 15:23:22 +0100 Message-ID: <6469744.tM3a2QDmDi@thomas> In-Reply-To: <8456f29c-2b76-7f82-1f70-6ac9612df5f@arknetworks.am> References: <20221114115946.1074787-1-rongweil@nvidia.com> <2807682.yaVYbkx8dN@thomas> <8456f29c-2b76-7f82-1f70-6ac9612df5f@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 01/02/2023 15:04, Ivan Malov: > On Wed, 1 Feb 2023, Thomas Monjalon wrote: > > The template flow API is experimental and will probably remain as such > > for a long time, so if you find a more elegant approach, > > we will consider it. > > Thanks for explaining this. > > You know, now you mention it, are there non-debug app > examples available that make use of this template API? > Back in the day, I reviewed the template API, but > since then, I've never come across any real-life > examples. I'd appreciate you point something out. I'm not aware of any Open Source project using the flow template API. But I can tell you that some companies are using it and it is the only way for them to reach their flow performance target. I would love to have an open router application truly based on DPDK.