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 8C22848B69 for ; Fri, 21 Nov 2025 12:24:46 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 85EF340395; Fri, 21 Nov 2025 12:24:46 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 810C7402EE for ; Fri, 21 Nov 2025 12:24:45 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1763724285; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=nB4Lv1wVQL3AAdjtAiWubEUYz/TIvv2j/thHKYhvwrU=; b=WkGQ847M6FgZfLEfAS8zlBnPDXltGKoCPghiXNN7an14VB8yOTGNd8XWBU6HYnSlRlHxev C1yqMlJqqsi+gE0gtmgHoL4I8oAZt1HA9sTBDn9C0js49wBkfy/qSdZVK49lRcTUSlEhpY /cqS3E5R/2KVeB0DpttlpQBH5xV6Qc0= Received: from mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-323-Epn1U8iOOGWZPUNZ0vSy1A-1; Fri, 21 Nov 2025 06:24:43 -0500 X-MC-Unique: Epn1U8iOOGWZPUNZ0vSy1A-1 X-Mimecast-MFC-AGG-ID: Epn1U8iOOGWZPUNZ0vSy1A_1763724282 Received: from mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id B291F195608A; Fri, 21 Nov 2025 11:24:42 +0000 (UTC) Received: from rh.redhat.com (unknown [10.42.28.165]) by mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 5E81F30044DB; Fri, 21 Nov 2025 11:24:41 +0000 (UTC) From: Kevin Traynor To: Itamar Gozlan Cc: Bing Zhao , dpdk stable Subject: patch 'net/mlx5/hws: fix flow rule hash capability' has been queued to stable release 24.11.4 Date: Fri, 21 Nov 2025 11:21:16 +0000 Message-ID: <20251121112128.485623-92-ktraynor@redhat.com> In-Reply-To: <20251121112128.485623-1-ktraynor@redhat.com> References: <20251121112128.485623-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.4 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: Ag_B0te_jkmlqxwbs1lklr6qjtCif7apFPCcmKrGq4M_1763724282 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit content-type: text/plain; charset="US-ASCII"; x-default=true X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Hi, FYI, your patch has been queued to stable release 24.11.4 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 11/26/25. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Queued patches are on a temporary branch at: https://github.com/kevintraynor/dpdk-stable This queued commit can be viewed at: https://github.com/kevintraynor/dpdk-stable/commit/8899362c43a2f24b8b4e37505a5e37ec589757ad Thanks. Kevin --- >From 8899362c43a2f24b8b4e37505a5e37ec589757ad Mon Sep 17 00:00:00 2001 From: Itamar Gozlan Date: Sun, 16 Nov 2025 13:59:25 +0200 Subject: [PATCH] net/mlx5/hws: fix flow rule hash capability [ upstream commit 970309c7aa889ee06178c6476fe153e17096fc25 ] Some cases are not supported for rule hash calculation. For example when the matcher defined as FW matcher, or is the hash type is different than CRC32. One case is when the distribute mode is not by hash, the previous condition checked a wrong capability, while this commit fixes it to the correct check. Fixes: 7f5e6de53aae ("net/mlx5/hws: query flow rule hash") Signed-off-by: Itamar Gozlan Acked-by: Bing Zhao --- drivers/net/mlx5/hws/mlx5dr_rule.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/mlx5/hws/mlx5dr_rule.c b/drivers/net/mlx5/hws/mlx5dr_rule.c index 519328ccf3..099f4f7947 100644 --- a/drivers/net/mlx5/hws/mlx5dr_rule.c +++ b/drivers/net/mlx5/hws/mlx5dr_rule.c @@ -1072,5 +1072,5 @@ int mlx5dr_rule_hash_calculate(struct mlx5dr_matcher *matcher, if (mlx5dr_matcher_req_fw_wqe(matcher) || mlx5dr_table_is_root(matcher->tbl) || - matcher->tbl->ctx->caps->access_index_mode == MLX5DR_MATCHER_INSERT_BY_HASH || + matcher->attr.distribute_mode != MLX5DR_MATCHER_DISTRIBUTE_BY_HASH || matcher->tbl->ctx->caps->flow_table_hash_type != MLX5_FLOW_TABLE_HASH_TYPE_CRC32) { DR_LOG(DEBUG, "Matcher is not supported"); -- 2.51.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2025-11-21 11:05:12.415345446 +0000 +++ 0092-net-mlx5-hws-fix-flow-rule-hash-capability.patch 2025-11-21 11:05:09.611165670 +0000 @@ -1 +1 @@ -From 970309c7aa889ee06178c6476fe153e17096fc25 Mon Sep 17 00:00:00 2001 +From 8899362c43a2f24b8b4e37505a5e37ec589757ad Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit 970309c7aa889ee06178c6476fe153e17096fc25 ] + @@ -13 +14,0 @@ -Cc: stable@dpdk.org @@ -22 +23 @@ -index 878224d8b3..895ac858ec 100644 +index 519328ccf3..099f4f7947 100644 @@ -25 +26 @@ -@@ -1085,5 +1085,5 @@ int mlx5dr_rule_hash_calculate(struct mlx5dr_matcher *matcher, +@@ -1072,5 +1072,5 @@ int mlx5dr_rule_hash_calculate(struct mlx5dr_matcher *matcher,