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 E579146BAE for ; Fri, 18 Jul 2025 21:36:33 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DC5BB40611; Fri, 18 Jul 2025 21:36:33 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id DC48F40E42 for ; Fri, 18 Jul 2025 21:36:31 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1752867391; 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=M28BDZeHNb3QuujPnWcbQwGOP9PrnSf9VSjpljRehDI=; b=QG3S/G+vho3M2H5TXyBdwZsR9VFhawFYw3hDWJOZna5vDxfwumwgI+mk6nsMqGDRSD/MOx 7Aj9jw8sep3R1Y0AGE9QauFBENMZQLIEDfa/D/PEBFAm09wJFW4QAMgnPUr3DmPVhtbnAC 220K5fzLCSW1zjYzJGoMP3H99CrkDLw= Received: from mx-prod-mc-03.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-608-4xol6IEzNgCkFoO5_Djhpw-1; Fri, 18 Jul 2025 15:36:28 -0400 X-MC-Unique: 4xol6IEzNgCkFoO5_Djhpw-1 X-Mimecast-MFC-AGG-ID: 4xol6IEzNgCkFoO5_Djhpw_1752867385 Received: from mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.93]) (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-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id AD1721977308; Fri, 18 Jul 2025 19:36:25 +0000 (UTC) Received: from rh.redhat.com (unknown [10.44.32.40]) by mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 6E677180045B; Fri, 18 Jul 2025 19:36:24 +0000 (UTC) From: Kevin Traynor To: Dengdui Huang Cc: dpdk stable Subject: patch 'net/hns3: allow Tx vector when fast free not enabled' has been queued to stable release 24.11.3 Date: Fri, 18 Jul 2025 20:30:35 +0100 Message-ID: <20250718193247.1008129-101-ktraynor@redhat.com> In-Reply-To: <20250718193247.1008129-1-ktraynor@redhat.com> References: <20250718193247.1008129-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.93 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: 5Vu2QiNgJVeFjx7JmGWb0FUQwZ7RQiwi85YCkwYFhp0_1752867385 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.3 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 07/23/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/544e88781a775aa758c769994d19b515b23eae5f Thanks. Kevin --- >From 544e88781a775aa758c769994d19b515b23eae5f Mon Sep 17 00:00:00 2001 From: Dengdui Huang Date: Mon, 9 Jun 2025 21:06:50 +0800 Subject: [PATCH] net/hns3: allow Tx vector when fast free not enabled [ upstream commit e05cb702ca70aecdf01041274cd6ffc9233a726d ] Currently, the Tx vector algorithm is only enabled when tx_offload is RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE. If no offloads are enabled, then vector algorithm can also be used. The vector algorithm does not support other transmit offloads. Fixes: e31f123db06b ("net/hns3: support NEON Tx") Signed-off-by: Dengdui Huang --- drivers/net/hns3/hns3_rxtx_vec.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/net/hns3/hns3_rxtx_vec.c b/drivers/net/hns3/hns3_rxtx_vec.c index 9708ec614e..c3d288ea5a 100644 --- a/drivers/net/hns3/hns3_rxtx_vec.c +++ b/drivers/net/hns3/hns3_rxtx_vec.c @@ -17,9 +17,9 @@ int hns3_tx_check_vec_support(struct rte_eth_dev *dev) { - struct rte_eth_txmode *txmode = &dev->data->dev_conf.txmode; + uint64_t tx_offloads = dev->data->dev_conf.txmode.offloads; struct rte_eth_rxmode *rxmode = &dev->data->dev_conf.rxmode; - /* Only support RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE */ - if (txmode->offloads != RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE) + /* Only support when Tx offloads is RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE or 0. */ + if (tx_offloads != RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE && tx_offloads != 0) return -ENOTSUP; -- 2.50.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2025-07-18 20:29:14.506978002 +0100 +++ 0101-net-hns3-allow-Tx-vector-when-fast-free-not-enabled.patch 2025-07-18 20:29:11.016992072 +0100 @@ -1 +1 @@ -From e05cb702ca70aecdf01041274cd6ffc9233a726d Mon Sep 17 00:00:00 2001 +From 544e88781a775aa758c769994d19b515b23eae5f Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit e05cb702ca70aecdf01041274cd6ffc9233a726d ] + @@ -12 +13,0 @@ -Cc: stable@dpdk.org @@ -20 +21 @@ -index bf37ce51b1..9fb66ea2de 100644 +index 9708ec614e..c3d288ea5a 100644