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 3D73845DB9 for ; Wed, 27 Nov 2024 18:22:55 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 37708402DE; Wed, 27 Nov 2024 18:22:55 +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 D6958402DE for ; Wed, 27 Nov 2024 18:22:53 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1732728173; 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=xb1ixdLg5NTBrRXflTegoDBCXKuclE4gA4sKdfh42jQ=; b=YwqLkCjZWQ+pmAcjdygKBwROn96UHQHLcBw+zUNgSXNToro/W25WesDV5B1PdG+3uN6zD1 HnUbm8d7xnYNz4UM3AKSXBd9jb8tsh2tu7CjRTT70BGQB7Ba8z91X6KZzh97NYimUA0aC7 HBHIRYS+KY8G3boBes0nd4ZxD7V/Zsg= Received: from mx-prod-mc-01.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-361-d5yFOIrSNOKBhpjFALp1nQ-1; Wed, 27 Nov 2024 12:22:49 -0500 X-MC-Unique: d5yFOIrSNOKBhpjFALp1nQ-1 X-Mimecast-MFC-AGG-ID: d5yFOIrSNOKBhpjFALp1nQ 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-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id D49731955BC9; Wed, 27 Nov 2024 17:22:48 +0000 (UTC) Received: from rh.redhat.com (unknown [10.39.192.52]) by mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 21A2230001A2; Wed, 27 Nov 2024 17:22:46 +0000 (UTC) From: Kevin Traynor To: Dengdui Huang Cc: Jie Hai , Stephen Hemminger , dpdk stable Subject: patch 'net/hns3: fix fully use hardware flow director table' has been queued to stable release 21.11.9 Date: Wed, 27 Nov 2024 17:18:42 +0000 Message-ID: <20241127171916.690404-95-ktraynor@redhat.com> In-Reply-To: <20241127171916.690404-1-ktraynor@redhat.com> References: <20241127171916.690404-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: SYpM3CS356NnQ__YlW2S7HlUTUIfrJsYNUvA5XJq2GM_1732728168 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 21.11.9 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 12/02/24. 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/47aec5f7f177af5c198e13cb3966c37691d03e63 Thanks. Kevin --- >From 47aec5f7f177af5c198e13cb3966c37691d03e63 Mon Sep 17 00:00:00 2001 From: Dengdui Huang Date: Thu, 7 Nov 2024 19:56:45 +0800 Subject: [PATCH] net/hns3: fix fully use hardware flow director table [ upstream commit b8e60c33168a2999604c17322dd0198a6746428f ] The hns3 driver checks whether the flow rule is repeatedly inserted based on rte_hash. Currently, the rte_hash extendable bucket table feature is not enabled. When there are many hash conflicts, the hash table space cannot be fully used. So the flow rule maybe cannot be inserted even if the hardware flow director table there are still free. This patch fix it by enabling the rte_hash extensible bucket table feature. Fixes: fcba820d9b9e ("net/hns3: support flow director") Signed-off-by: Dengdui Huang Signed-off-by: Jie Hai Acked-by: Stephen Hemminger --- drivers/net/hns3/hns3_fdir.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/hns3/hns3_fdir.c b/drivers/net/hns3/hns3_fdir.c index a2dd25fb21..5a1dde1786 100644 --- a/drivers/net/hns3/hns3_fdir.c +++ b/drivers/net/hns3/hns3_fdir.c @@ -833,4 +833,5 @@ int hns3_fdir_filter_init(struct hns3_adapter *hns) .hash_func = rte_hash_crc, .hash_func_init_val = 0, + .extra_flag = RTE_HASH_EXTRA_FLAGS_EXT_TABLE, }; int ret; -- 2.47.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2024-11-27 17:17:41.250129000 +0000 +++ 0095-net-hns3-fix-fully-use-hardware-flow-director-table.patch 2024-11-27 17:17:38.304269783 +0000 @@ -1 +1 @@ -From b8e60c33168a2999604c17322dd0198a6746428f Mon Sep 17 00:00:00 2001 +From 47aec5f7f177af5c198e13cb3966c37691d03e63 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit b8e60c33168a2999604c17322dd0198a6746428f ] + @@ -15 +16,0 @@ -Cc: stable@dpdk.org @@ -25 +26 @@ -index d18d083535..aacad40e61 100644 +index a2dd25fb21..5a1dde1786 100644 @@ -28 +29 @@ -@@ -901,4 +901,5 @@ int hns3_fdir_filter_init(struct hns3_adapter *hns) +@@ -833,4 +833,5 @@ int hns3_fdir_filter_init(struct hns3_adapter *hns)