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 5403CA0093; Tue, 4 Jan 2022 13:42:00 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D29FE40040; Tue, 4 Jan 2022 13:41:59 +0100 (CET) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id AD0ED4003C for ; Tue, 4 Jan 2022 13:41:58 +0100 (CET) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 009435C00AE; Tue, 4 Jan 2022 07:41:58 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Tue, 04 Jan 2022 07:41:58 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm3; bh= DnCE0eQMXBX5l4biUgCOuuiGUJ+JFZ+YOsPwtYzpiqQ=; b=KfYTlm5BjOhTkKPo 5XvgtSF/Xf/FHAPkqWZ2w4Fn3D9I88uZnQkEvLBxH/jQVIq+R7ZnieP65pDg5JjN 1CU5moQ6eJ3GNfCol84iGp6mib3c43c1pTG/Tfmo7yFCU/iwXxmcGcYvskpH7XVj Pz0BduhdG4QuNUTkxByaLFN69bcw0gTz2HGy7GnV5CgudcXON73XeoGPbyLE10sH v3ARhQIOQlBHHHxpJ5QqhPSfRHpl6HLZ9ASEG6P5PBOKNgIq9IHdUmBNvxk6lZMs Kb+UzMqwkWN4f9t5EmJKTHkXokeNvXUdWAeTCETlgxeQb8kCfqunrhno9Ywj9Z0C 5e2wjQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=DnCE0eQMXBX5l4biUgCOuuiGUJ+JFZ+YOsPwtYzpi qQ=; b=QfEzr5R7b5cNLJg/cdHIJwO4GF/roXZ5TcpC1AQS3DvhVISSCRU1JNDjJ oKCLU26FIFbTxaeZwCWuK2qBucOrIxYGfBTd0O8/G76rBeGrvdj/bk4c9ijL+DkN neNxJefld8Qy8vN5AeR5QIW57Zh2K+7Ibf7WKu98GmBPuP3sKobb0Xyq4lSQ1F6n V4E+ubb34eriDZyufBAR82iU92MluQN2IksKVXgq9VSbRLGsZeRx9xKrxcE3YW32 dAFwzeuFXLvG/z1JHwKxfqqZcogoQrhvERFPJ/Em86oVrgQom59lXJLzQxP2VdYa hfbFElrh8zRkd+o26eN/2op6nNjJQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrudeffedggeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeu ieeivdffgeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 4 Jan 2022 07:41:56 -0500 (EST) From: Thomas Monjalon To: Ivan Malov Cc: Adrien Mazarguil , dev@dpdk.org, Andrew Rybchenko , orika@nvidia.com Subject: Re: Understanding Flow API action RSS Date: Tue, 04 Jan 2022 13:41:55 +0100 Message-ID: <4677833.GXAFRqVoOG@thomas> In-Reply-To: <76f98055-c517-5185-b79-d16ec5ef5ff@oktetlabs.ru> References: <76f98055-c517-5185-b79-d16ec5ef5ff@oktetlabs.ru> 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 +Cc Ori Kam, rte_flow maintainer 29/12/2021 15:34, Ivan Malov: > Hi all, > > In 'rte_flow.h', there is 'struct rte_flow_action_rss'. In it, 'queue' is > to provide "Queue indices to use". But it is unclear whether the order of > elements is meaningful or not. Does that matter? Can queue indices repeat? > > An ethdev may have "global" RSS setting with an indirection table of some > fixed size (say, 512). In what comes to flow rules, does that size matter? > > When the user selects 'RTE_ETH_HASH_FUNCTION_DEFAULT' in action RSS, does > that allow the PMD to configure an arbitrary, non-Toeplitz hash algorithm? > > Please advise.