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 B7C4546BAE for ; Fri, 18 Jul 2025 21:38:07 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id AEAFD40611; Fri, 18 Jul 2025 21:38:07 +0200 (CEST) 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 B821E40611 for ; Fri, 18 Jul 2025 21:38:06 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1752867486; 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=d5WgHJmAfEIz7bi8baF19vmbxk0+M22utU1tX7KS/7s=; b=gSBzcalLKUi9ba17v+N20wVH/EUIpZJrl4NeyEJX2X2YgDZmjxEr99tzJKO5UZJTOSuag/ etjIA0d77uGY/8jkVtQulHGefe4MBYKY73hzwAmnjAsYuu0zsgmm3ECzsDpFWzvoNVDgow 4FGNdqPbHGmQt0UFDqMJJmwzPnt980A= 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-511-MXf89YK3OyOFoZRLb6o98Q-1; Fri, 18 Jul 2025 15:38:03 -0400 X-MC-Unique: MXf89YK3OyOFoZRLb6o98Q-1 X-Mimecast-MFC-AGG-ID: MXf89YK3OyOFoZRLb6o98Q_1752867482 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-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 290BD195FCC2; Fri, 18 Jul 2025 19:38:02 +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 DD15B180049D; Fri, 18 Jul 2025 19:38:00 +0000 (UTC) From: Kevin Traynor To: Jiawen Wu Cc: dpdk stable Subject: patch 'net/txgbe: add LRO flag in mbuf when enabled' has been queued to stable release 24.11.3 Date: Fri, 18 Jul 2025 20:31:23 +0100 Message-ID: <20250718193247.1008129-149-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: HccKI4CnhFNXS2fDfqqTR5urukNH14Tk_4P0KeRajAU_1752867482 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/7561876ee31af8ff142bb4c1a90a6dc62f8bd8aa Thanks. Kevin --- >From 7561876ee31af8ff142bb4c1a90a6dc62f8bd8aa Mon Sep 17 00:00:00 2001 From: Jiawen Wu Date: Fri, 13 Jun 2025 16:41:59 +0800 Subject: [PATCH] net/txgbe: add LRO flag in mbuf when enabled [ upstream commit 5bc6a8b17afbf299773a70315ad95262d8f6d0ac ] When LRO is enabled, the driver must set the LRO flag in received aggregated packets to indicate LRO processing to upper-layer applications. Add the missing LRO flag into the ol_flags field of mbuf to fix it. Fixes: 0e484278c85f ("net/txgbe: support Rx") Signed-off-by: Jiawen Wu --- drivers/net/txgbe/txgbe_rxtx.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/net/txgbe/txgbe_rxtx.c b/drivers/net/txgbe/txgbe_rxtx.c index 4e4b78fb43..46e73a89cb 100644 --- a/drivers/net/txgbe/txgbe_rxtx.c +++ b/drivers/net/txgbe/txgbe_rxtx.c @@ -1794,4 +1794,6 @@ txgbe_fill_cluster_head_buf(struct rte_mbuf *head, struct txgbe_rx_desc *desc, pkt_flags |= rx_desc_error_to_pkt_flags(staterr); pkt_flags |= txgbe_rxd_pkt_info_to_pkt_flags(pkt_info); + if (TXGBE_RXD_RSCCNT(desc->qw0.dw0)) + pkt_flags |= RTE_MBUF_F_RX_LRO; head->ol_flags = pkt_flags; head->packet_type = txgbe_rxd_pkt_info_to_pkt_type(pkt_info, -- 2.50.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2025-07-18 20:29:16.224307688 +0100 +++ 0149-net-txgbe-add-LRO-flag-in-mbuf-when-enabled.patch 2025-07-18 20:29:11.129907941 +0100 @@ -1 +1 @@ -From 5bc6a8b17afbf299773a70315ad95262d8f6d0ac Mon Sep 17 00:00:00 2001 +From 7561876ee31af8ff142bb4c1a90a6dc62f8bd8aa Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit 5bc6a8b17afbf299773a70315ad95262d8f6d0ac ] + @@ -12 +13,0 @@ -Cc: stable@dpdk.org @@ -20 +21 @@ -index a85d417ff6..e6f33739c4 100644 +index 4e4b78fb43..46e73a89cb 100644