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 A83AAA0543 for ; Fri, 4 Nov 2022 17:52:07 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3753842D12; Fri, 4 Nov 2022 17:52:07 +0100 (CET) Received: from mail-pj1-f41.google.com (mail-pj1-f41.google.com [209.85.216.41]) by mails.dpdk.org (Postfix) with ESMTP id 959C642D10 for ; Fri, 4 Nov 2022 17:52:05 +0100 (CET) Received: by mail-pj1-f41.google.com with SMTP id d59-20020a17090a6f4100b00213202d77e1so8756016pjk.2 for ; Fri, 04 Nov 2022 09:52:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=ZkRKUlPi+RRn4MB7HD5wMPR08LaDIveeJRFwI0eQpnY=; b=7dxz/egpRC2GsFVTOOFBBv6+5xd1gOlnym/FzNEQUyfCUtq7VMBCZxYpTwDMmEDLO1 mXiTvtfH7BnprGQs7nBBqMMf5+dDVVc/NJrv0o9Q4WsP035q7Ei7AHmsZxriFAfs5rJM 2Vrru4bMlub21baHiM3tFlTrvxAxwJe3qhSUeEOkBxEklmLOMSmV4+K4lAge88VrtrdI H+0KGYTy6gGhYQjWO1eGXXHA6P8CPedyirdnDnbLXxAc82PcGlJrSr7wuFi84dRXsKHQ c5cSayBEnjf/oKyvQmUwdLT6a+b46aNaFRrpqAIUKIzymZTCtK9xpaYuy/E+EFrFasI+ mG1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ZkRKUlPi+RRn4MB7HD5wMPR08LaDIveeJRFwI0eQpnY=; b=w31JYgmzv1/NPYfYRDUH4vpRMIG21HsLhNg9MQt/FPuiVkPAAICWy8n6OyQD14HA2R qesFOPIQSoc1/aGTbqacUWHQY9OYLDHzNDQb7GmwI+5P+8ZSsarI1kEOqlkbuxIrTmIn 2l+kD26i/Qzzw3WQuvA/CbDQex911Djcld+jUmsOG45nINLby0m4oNUFgylBFEk3igsx HonMwYkE1wS7Ja6y8Q/B3iAgbLlVh8uKyV26H8hZKSZ7VAeREzPgPRwbQ5eBqgk5w6wm KNQKJaEVOgmEkK2d7wlV2YYoP/bE5b/bLy8AacRhMWG+6+65q8Whqu6jpg97iivabbMB cv5Q== X-Gm-Message-State: ACrzQf3sMy1LhHkYSkzV5dr9UwtABErykiVbkO4GadN+Vd1jefEWIfNR kXqOLBu0xEKuqM7NcBPdY1ecBo6e09P2DQ== X-Google-Smtp-Source: AMsMyM7bfLoi8fSoDRdAyNWzrH+1QkQPUPdoORd1pN9t1RbtTRE8/mEwdMthvmsjXT8UXBp3PyD1JA== X-Received: by 2002:a17:90a:5517:b0:213:b122:41b3 with SMTP id b23-20020a17090a551700b00213b12241b3mr35233532pji.121.1667580724203; Fri, 04 Nov 2022 09:52:04 -0700 (PDT) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id d14-20020a170902654e00b0017e9b820a1asm2883403pln.100.2022.11.04.09.52.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 04 Nov 2022 09:52:03 -0700 (PDT) Date: Fri, 4 Nov 2022 09:52:02 -0700 From: Stephen Hemminger To: Yang Luan Cc: users@dpdk.org Subject: Re: Wrong rx queue assignment running DPDK on Azure Message-ID: <20221104095202.32c55020@hermes.local> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org On Tue, 1 Nov 2022 17:25:24 -0700 Yang Luan wrote: > Hello, >=20 >=20 > Our application uses the net_netvsc driver in DPDK 21.08 on Azure. We fou= nd > an issue where RSS doesn=E2=80=99t deliver packets to the correct rx queu= e. The > instance type we use is Standard_L80s_v3 with MT27800 Family [ConnectX-5 > Virtual Function] NICs. The NIC is configured with 40 rx queues and the > RETA table is configured (confirmed by rte_eth_dev_rss_reta_query()) as > below. >=20 >=20 >=20 > 0: 0 1 2 3 4 5 6 7 >=20 > 8: 8 9 10 11 12 13 14 15 >=20 > 16: 16 17 18 19 20 21 22 23 >=20 > 24: 24 25 26 27 28 29 30 31 >=20 > 32: 32 33 34 35 36 37 38 39 >=20 > 40: 0 1 2 3 4 5 6 7 >=20 > 48: 8 9 10 11 12 13 14 15 >=20 > 56: 16 17 18 19 20 21 22 23 >=20 > 64: 24 25 26 27 28 29 30 31 >=20 > 72: 32 33 34 35 36 37 38 39 >=20 > 80: 0 1 2 3 4 5 6 7 >=20 > 88: 8 9 10 11 12 13 14 15 >=20 > 96: 16 17 18 19 20 21 22 23 >=20 > 104: 24 25 26 27 28 29 30 31 >=20 > 112: 32 33 34 35 36 37 38 39 >=20 > 120: 0 1 2 3 4 5 6 7 >=20 >=20 >=20 > One example is a packet received with rss key 0xEDE25D84 was incorrectly > delivered to rx queue 12. We expect it to be queue 4 as 0xEDE25D84 & 0x7F= =3D > 4 assuming seven of the least significant bits (LSBs) are used for indexi= ng > into the RETA table. Is it a bug or we made a wrong assumption on how the > RETA table is accessed with that device? >=20 >=20 > Thank you. >=20 > Yang Are you using failsafe PMD or the native netvsc PMD? Are you programming reta table via DPDK or through other API's?