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 4B61745701; Wed, 31 Jul 2024 15:02:17 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3B4B240F1A; Wed, 31 Jul 2024 15:02:17 +0200 (CEST) Received: from fhigh5-smtp.messagingengine.com (fhigh5-smtp.messagingengine.com [103.168.172.156]) by mails.dpdk.org (Postfix) with ESMTP id 3F6BD40E09 for ; Wed, 31 Jul 2024 15:02:16 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailfhigh.nyi.internal (Postfix) with ESMTP id DAAC11146CE4; Wed, 31 Jul 2024 09:02:15 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 31 Jul 2024 09:02:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1722430935; x=1722517335; bh=44ej1J1TwueOv9I5AYVAvnQuj8cveXaY9vkVayMMo1k=; b= AeEiwF/BCCNMnb6GIBl8etZnOx5Q8O1jvHV9klL0OylTq7UivCP/S9VeRTzV74pw 0fVlNbTMVLjLuymHtvg/kBOdLa34tZVpkSu+3/KJEIAicLqyzGd7dMYTtBC/j+hi 57G7cD49mfqu06mUB6Egg4X0G71ss3YTBOstBkyLfqHyM+5OREy/Nn9j06nj3OiA kE0sku97PXLodV8T9rL4w5KB1Wst/sRE8NmaWoTuvyQEBAWebpt0X+0NhKVsd8Wd OfU/pW/NxJqzr4UoBry318wJRtK2SFHPBwlpDkpqf+Z/q5/z8PGjtJcG8CbNZ4gR yeJkRirlc7JBiPGmyVJ5Vw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1722430935; x= 1722517335; bh=44ej1J1TwueOv9I5AYVAvnQuj8cveXaY9vkVayMMo1k=; b=q sBrAtcIcPCm7HX5M9ShwcnMcbumFxhcO1R3ECNRSw5X7QIqjam+kJALjI6dsaAlG lBd2fHoSLXOO7YP431vZKyc/rr82zvSlVbWRDhiO8fA/iyybiUC8PZZvEkH+sd0s ZiSXf4P/+IKVu4iCaAcHSlOk2jnnozZo1+iaQdwY/ch51Z5CDBghR/3nyw6NgzQF cSY3FnNijcscxVDodddjEZjH0zr1IgT3rSw/rtwYXcIDG5Mhhx7/En0hc5SGexbq T3FM1pzSYGAIkRN1c23yslXGFbVRi7FNDAHiG1K+HHydnzuXNgtF6tz0GeRsT4Ml Q0xJ2DbYkXZQrA7VU0Z+w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrjeeigdeitdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvfevufffkfgjfhgggfgtsehtufertddttdejnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepkeefheeftdegtdejheeuuedtgfelfeeiveekieekleekffelgfdt veeiheehffdunecuffhomhgrihhnpeguphgukhdrohhrghenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhn rdhnvghtpdhnsggprhgtphhtthhopedt X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 31 Jul 2024 09:02:14 -0400 (EDT) From: Thomas Monjalon To: Alex Chapman Cc: dev@dpdk.org, Luca.Vizzarro@arm.com, Paul.Szczepanek@arm.com, Dariusz Sosnowski , Viacheslav Ovsiienko , Bing Zhao , Ori Kam , Suanming Mou , Matan Azrad Subject: Re: Issue in testpmd when using RSS Flows with Mellanox NICs Date: Wed, 31 Jul 2024 15:02:12 +0200 Message-ID: <2103021.K71DO8KEF6@thomas> In-Reply-To: <8adf2621-3202-4eff-ab9b-61cdbfc901ad@arm.com> References: <8adf2621-3202-4eff-ab9b-61cdbfc901ad@arm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" 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 Hello, 31/07/2024 14:55, Alex Chapman: > Hello maintainers, Do not hesitate to read the file MAINTAINERS to place the appropriate Cc list. Adding mlx5 maintainers. > I am currently facing issues when creating RSS flows using testpmd. > When using the following flow on an intel NIC, it works as expected, > using the reta table to redirect ipv4-udp packets to the correct queue. > > flow create 0 ingress pattern eth / ipv4 / udp / end actions rss types > ipv4-udp end queues end func toeplitz / end > > However when executing the same command on a Mellanox NIC, the following > error occurs. > > Caught PMD error type 15 (action configuration): No queues > configured: Invalid argument > > This error can be resolved by manually specifying the queues used: > > flow create 0 ingress pattern eth / ipv4 / udp / end actions rss > types ipv4-udp end queues 0 1 2 3 4 5 6 7 8 end func toeplitz / end > > However the packets are not placed into their expected queues using the > reta table. > > When looking through the Generic flow API guide under RSS > (https://doc.dpdk.org/guides/prog_guide/rte_flow.html), the attribute > queues does not exist. > From my understanding this seems to be a mistake, as the attribute > "queue" does exist with the definition "queue indices to use" > However when attempting to use this attribute I get the error "Bad > arguments" > > If anyone is able to shed some light on the use of RSS in flows, that > would be greatly appreciated. > > Thanks, > Alex