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 BEAD5A0353; Thu, 24 Feb 2022 09:22:20 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6600041155; Thu, 24 Feb 2022 09:22:20 +0100 (CET) Received: from shelob.oktetlabs.ru (shelob.oktetlabs.ru [91.220.146.113]) by mails.dpdk.org (Postfix) with ESMTP id 038764114D for ; Thu, 24 Feb 2022 09:22:18 +0100 (CET) Received: from [192.168.38.17] (aros.oktetlabs.ru [192.168.38.17]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by shelob.oktetlabs.ru (Postfix) with ESMTPSA id 2DB2A56; Thu, 24 Feb 2022 11:22:17 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 shelob.oktetlabs.ru 2DB2A56 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=oktetlabs.ru; s=default; t=1645690938; bh=Unvo8N892L+m2BGAvYjoImoYK2qA9j2mwVI/Y8rnbPM=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=us+0wJ6tBvOo0m4gYZscN4LEGHOXycePrpALcQB/tQ5n3FjRrVNVbn6V3gOuoDSz5 fn1p8VGUDDMNWDZZRc3JxLCHv4cBr+ivh3Uwn3HB9vRmYosIRljKBoV7Kk+b63FIFv Oc5F+RAMmmySuqq6I1VM3oGwz4S6rJ/rog165vH4= Message-ID: <62ba5053-8540-587b-0611-b706df0bdf4e@oktetlabs.ru> Date: Thu, 24 Feb 2022 11:22:15 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: [PATCH v10 01/11] ethdev: introduce flow engine configuration Content-Language: en-US To: Alexander Kozyrev , dev@dpdk.org Cc: orika@nvidia.com, thomas@monjalon.net, ivan.malov@oktetlabs.ru, ferruh.yigit@intel.com, mohammad.abdul.awal@intel.com, qi.z.zhang@intel.com, jerinj@marvell.com, ajit.khaparde@broadcom.com, bruce.richardson@intel.com References: <20220221230240.2409665-1-akozyrev@nvidia.com> <20220223030240.2506513-1-akozyrev@nvidia.com> <20220223030240.2506513-2-akozyrev@nvidia.com> From: Andrew Rybchenko Organization: OKTET Labs In-Reply-To: <20220223030240.2506513-2-akozyrev@nvidia.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 On 2/23/22 06:02, Alexander Kozyrev wrote: > The flow rules creation/destruction at a large scale incurs a performance > penalty and may negatively impact the packet processing when used > as part of the datapath logic. This is mainly because software/hardware > resources are allocated and prepared during the flow rule creation. > > In order to optimize the insertion rate, PMD may use some hints provided > by the application at the initialization phase. The rte_flow_configure() > function allows to pre-allocate all the needed resources beforehand. > These resources can be used at a later stage without costly allocations. > Every PMD may use only the subset of hints and ignore unused ones or > fail in case the requested configuration is not supported. > > The rte_flow_info_get() is available to retrieve the information about > supported pre-configurable resources. Both these functions must be called > before any other usage of the flow API engine. > > Signed-off-by: Alexander Kozyrev > Acked-by: Ori Kam Reviewed-by: Andrew Rybchenko