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 0CADE44034; Wed, 15 May 2024 10:31:16 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 71CB5402BE; Wed, 15 May 2024 10:31:15 +0200 (CEST) Received: from mail-ed1-f54.google.com (mail-ed1-f54.google.com [209.85.208.54]) by mails.dpdk.org (Postfix) with ESMTP id 38CDD4021D for ; Wed, 15 May 2024 10:20:51 +0200 (CEST) Received: by mail-ed1-f54.google.com with SMTP id 4fb4d7f45d1cf-56e37503115so914576a12.1 for ; Wed, 15 May 2024 01:20:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715761250; x=1716366050; darn=dpdk.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=9cIa5lt9bjS5D+zIeHTuvNenE9gjtY9lffLcTHdFRg4=; b=OAGnQrtc1H/X5wyBORHXemsX+aXmTZyNAUzKSAPQbBTAeMiootZqufiaFUe5U/0T73 CRaxro+da95jPV1OjVZ0N1N1B38zmrPhqMcNFXU0MS2aj56tKFehOceeUdo2rECSeHS6 pAd0QDB5/YVzui780WH6T5d9rMnrRsTcMF0I+PYZNkqvQwaKDsY71F24nQlbQxiUQPUE 9HaNpqNNSFjURfFTvRVbqyFuykH6ppSw5gFlaH6g6j1SXs84cwPcKYWT1ovdODrlSR57 H6cD8wjgd21C8/ssgLygCSuWAp8nYiWUj1C7/T5NC9T6ILEDR37lL15AVSm/xDnefFBY JWzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715761250; x=1716366050; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=9cIa5lt9bjS5D+zIeHTuvNenE9gjtY9lffLcTHdFRg4=; b=vBXExaOzK2TqGNXwq5IP8S8iA3Iif77sWdAJKJQrRL89s4BQgsMAk8PnauLlXnN2V1 nVyGu1m5BrQ92vX6klpeGLeBp4NVbN4lKwQYe2XboDA4p3BT2I2VBi071CG0LKoL4Y+Y v3M9Tmvd5vGl908gNsucN7P3iJnTlUzvJIsTJke8xjsdsBfar0bqZCelTQdo/MZ++d// 8MhnpuibY11V99kOMTwjR3kciaH3enaI+Wq4Xv6NK9w6ZurpEoOhwcXDSN+tms6b2sda 3FxRan3Z2eEhvqh1BUWs62826/RkaiayL9m4w7WOiFpGBg9wfi/XpKxJzqmgffCpeczE NUjQ== X-Gm-Message-State: AOJu0Yw377IDlT19S0d3MSnugg0e7FgXieYRMVBXSuy2cRQPcHFtJWnV FF5zpAaVUKbdyy6/VeqpSslL8t+7ZTrbNFuUvZetU4E7nPAi+Ux5zmsnB3rqPmaWSA1DZ/n3Q4p nmpGMnSxm7b1Tv6ykpQ9Pv0p2ySSZl6I= X-Google-Smtp-Source: AGHT+IF/k77b2/D20XLDbNzQrL7dzUX5IlnrmrfCwKVKXpYKbzxyqk9wv5DWeAXIX8BWw1WgHdF3iBPQDnVsCRgu4Hc= X-Received: by 2002:a17:906:b0ca:b0:a59:9c58:763a with SMTP id a640c23a62f3a-a5a2d5ccb27mr970661766b.46.1715761250174; Wed, 15 May 2024 01:20:50 -0700 (PDT) MIME-Version: 1.0 From: Nagesh Mallappa Date: Wed, 15 May 2024 13:50:38 +0530 Message-ID: Subject: RSS Hash value returned by the gvnic pmd dpdk driver not matching Toeplitz To: dev@dpdk.org Content-Type: multipart/alternative; boundary="000000000000d60f1e061879cb04" X-Mailman-Approved-At: Wed, 15 May 2024 10:31:13 +0200 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 --000000000000d60f1e061879cb04 Content-Type: text/plain; charset="UTF-8" Hi Team, We are using a C3 GCP instance having GVNIC with DPDK enabled. We are using latest version of DPDK ( dpdk-24.03 ) to configure RSS key, we understand C3 GCP instance with gvnic supports Toeplitz rss algorithm ( Reference - https://github.com/google/compute-virtual-ethernet-dpdk/blob/main/gve_ethdev.c ), but we are hitting below issue. *Problem Statement - The RSS Hash value returned by the gvnic driver is different and is not matching the one computed by Toeplitz.* Using below script to compute rss hash value from Toeplitz. (https://gist.github.com/joongh/16867705b03b49e393cbf91da3cb42a7) Consider below data to compute RSS Hash value - Source IP - 79.124.62.122 Destination IP - 192.168.7.28 Source Port - 49442 Destination Port - 55327 RSS Key - {0x94e3e97e, 0x4abac401, 0x1e0edbf, 0xe059e1f4, 0xb6e27dff, 0xdf55c916, 0xe9e6e4db, 0x1f9fb82c, 0x1e0edbf, 0xe059e1f4} *Hash Value returned by Toeplitz - 0x8bbafd0f* Gvnic dpdk pmd driver which uses Toeplitz RSS hash algorithm too is expected to compute above RSS Hash value but we see the Hash value stored in dpdk mbuf to be 0xc6a15941 which is not right. >From the DPDK side we have ensured RSS offloading configuration is done appropriately, but still we are seeing above mismatch. We request you to please help us understand why this mismatch is happening and is this expected behavior of gvnic on C3 instance. Thanks, Nagesh --000000000000d60f1e061879cb04 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Team,

We are using a C3 GCP instance having GVN= IC with DPDK enabled.
We are using lates= t version of DPDK ( dpdk-24.03 ) to configure RSS key, we understand C3 GCP= instance with gvnic supports Toeplitz rss algorithm ( Reference -=C2=A0h= ttps://github.com/google/compute-virtual-ethernet-dpdk/blob/main/gve_ethdev= .c=C2=A0), but we are hitting below issue.

Problem Statement - The RSS Hash value returned by the gvnic driver is = different and is not matching the one computed by Toeplitz.

Using below sc= ript to compute rss hash value from Toeplitz.
(https:= //gist.github.com/joongh/16867705b03b49e393cbf91da3cb42a7)

Consider below data = to compute RSS Hash value -

Source IP - 79.124.62.122
Destination IP - 192.168.7.28
Sour= ce Port - 49442
Destination Port - 55327=
RSS Key - {0x94e3e97e, 0x4abac401, 0x1e= 0edbf, 0xe059e1f4, 0xb6e27dff, 0xdf55c916, 0xe9e6e4db, 0x1f9fb82c, 0x1e0edb= f, 0xe059e1f4}

Hash Value returned by Toepl= itz - 0x8bbafd0f

Gvnic dpdk pmd driver which uses Toeplitz RSS hash algori= thm too is expected to compute above RSS Hash value but we see the Hash val= ue stored in dpdk mbuf to be 0xc6a15941 which is not right.
From the DPDK side we have ensured RSS offloading confi= guration is done appropriately, but still we are seeing above mismatch.

=

We request = you to please help us understand why this mismatch is happening and is this= expected behavior of gvnic on C3 instance.

Thanks,

Nagesh

--000000000000d60f1e061879cb04--