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 1E287A0542 for ; Thu, 24 Nov 2022 15:01:03 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 24C0942DD9; Thu, 24 Nov 2022 15:01:02 +0100 (CET) Received: from smtp-relay-internal-0.canonical.com (smtp-relay-internal-0.canonical.com [185.125.188.122]) by mails.dpdk.org (Postfix) with ESMTP id 4E6AD42DCA for ; Thu, 24 Nov 2022 15:01:01 +0100 (CET) Received: from mail-ed1-f69.google.com (mail-ed1-f69.google.com [209.85.208.69]) (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 smtp-relay-internal-0.canonical.com (Postfix) with ESMTPS id 156AA3F176 for ; Thu, 24 Nov 2022 14:01:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1669298461; bh=gfY/tmTOSnQ8m3C28e0TaTgFYAqyv4dkSWRLJGljROs=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=FJdVV2UH3wPOaboKcn5t2o+OZdz1O/PxyvN2D40uM/wrHmZCWOI8zsEw+nm6oxP0V 8n+qW5JB6Vu1/w2URsmNQWe0NwmqW3kBTxRgWaSnJoSPWs5DMOMlpMndvHC2t4q6F8 QVC7t1MG4/9wXe5YHYh3Z2gpciaUREyzHqV6c8hGfeIjknlswbGnmOAHNVakf+y5jR Pcta1uUayz6uIG6k+Xc4pkZB8rsP3trErn1scMmas5ctO8ZcWos4F3o2YfkanuScBZ LCqbJxzOXZUsEnxRFnPotZXu8JPIosCfsX78r1g0WIlkoBPFRCC1HT7R5kynZDy1s3 Mr0eqQDWgMl9Q== Received: by mail-ed1-f69.google.com with SMTP id l18-20020a056402255200b004633509768bso984691edb.12 for ; Thu, 24 Nov 2022 06:01:01 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=gfY/tmTOSnQ8m3C28e0TaTgFYAqyv4dkSWRLJGljROs=; b=KCD1AMpt8EVpd78OYO4cO4n3iR1mq1jrnAjhNqop6Lrl0YabrBn3+4ER9vyF4cgeno 6uu0Mczn5YtYBixxgKBtieJdSScHYAouTOOBMEoJB9z/RfXaSgeKR0ASg6CdJM5vXFhe NOcURfB9RpcjCGu+DabF89B6unmBsYJkmPCwSGAfT3bfQVp5zuN2gUUdZu70IVXNYGBG PuG/kUFFpd58YXcuIhD2XRluzLxRcwFGQkF9WcmpglAklOinfkPpzXgMKOjbYxq6px6i AXMMl/o0pI1BxtOlTDiRhU4hzPfLj3vwsEY3ebdJvfiC/7H/kpWLFYZSpz8D3RQ62I9N 846g== X-Gm-Message-State: ANoB5pmpnNc81OVZBKWHREMtsbDkFbQhJwBQyt2GC5yHWUq90dlSAX8a ifGWjq2ePW8NDvGxVvP9wzZqfgR7qJdAVG2AbOevVDMPafNkSYVDsnaoO/ZHtxkgt/eCBVe8w4I AMeCgKSRZzjbnseZOtG28/iji X-Received: by 2002:a17:906:11d6:b0:7ba:5c15:97c with SMTP id o22-20020a17090611d600b007ba5c15097cmr5290093eja.439.1669298460426; Thu, 24 Nov 2022 06:01:00 -0800 (PST) X-Google-Smtp-Source: AA0mqf5yk+OvKrSSjXEEmDqs8C4wUEDifdOoISunUhtcRuu4cuWdT9cX9eEiGo3jqAgzl8yDVzWn7w== X-Received: by 2002:a17:906:11d6:b0:7ba:5c15:97c with SMTP id o22-20020a17090611d600b007ba5c15097cmr5290071eja.439.1669298460122; Thu, 24 Nov 2022 06:01:00 -0800 (PST) Received: from localhost.localdomain ([2a02:6d40:39e5:dd00:978:e124:4bf:b342]) by smtp.gmail.com with ESMTPSA id u17-20020aa7d0d1000000b004617e880f52sm544478edo.29.2022.11.24.06.00.58 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 24 Nov 2022 06:00:59 -0800 (PST) From: christian.ehrhardt@canonical.com To: Gregory Etelson Cc: Matan Azrad , dpdk stable Subject: patch 'doc: add LRO size limitation in mlx5 guide' has been queued to stable release 19.11.14 Date: Thu, 24 Nov 2022 15:00:33 +0100 Message-Id: <20221124140034.770192-10-christian.ehrhardt@canonical.com> X-Mailer: git-send-email 2.38.1 In-Reply-To: <20221124140034.770192-1-christian.ehrhardt@canonical.com> References: <20221124140034.770192-1-christian.ehrhardt@canonical.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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 19.11.14 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/22. 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/cpaelzer/dpdk-stable-queue This queued commit can be viewed at: https://github.com/cpaelzer/dpdk-stable-queue/commit/7affcdababda623d2638ece56bb2334e3e7597fa Thanks. Christian Ehrhardt --- >From 7affcdababda623d2638ece56bb2334e3e7597fa Mon Sep 17 00:00:00 2001 From: Gregory Etelson Date: Thu, 17 Nov 2022 16:39:01 +0200 Subject: [PATCH] doc: add LRO size limitation in mlx5 guide [ upstream commit ea75808941c8020c568e47d1ef9b25223258c131 ] Maximal LRO message size must be multiply of 256. Otherwise, TCP payload may not fit into a single WQE. Fixes: 1c7e57f9bd33 ("net/mlx5: set maximum LRO packet size") Signed-off-by: Gregory Etelson Acked-by: Matan Azrad --- doc/guides/nics/mlx5.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst index 8f7b285271..5d2ffe416c 100644 --- a/doc/guides/nics/mlx5.rst +++ b/doc/guides/nics/mlx5.rst @@ -226,6 +226,8 @@ Limitations TCP header (122B). - Rx queue with LRO offload enabled, receiving a non-LRO packet, can forward it with size limited to max LRO size, not to max RX packet length. + - The driver rounds down the port configuration value ``max_lro_pkt_size`` + (from ``rte_eth_rxmode``) to a multiple of 256 due to hardware limitation. - Timestamps: -- 2.38.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2022-11-24 14:58:14.591197334 +0100 +++ 0010-doc-add-LRO-size-limitation-in-mlx5-guide.patch 2022-11-24 14:58:11.841189674 +0100 @@ -1 +1 @@ -From ea75808941c8020c568e47d1ef9b25223258c131 Mon Sep 17 00:00:00 2001 +From 7affcdababda623d2638ece56bb2334e3e7597fa Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit ea75808941c8020c568e47d1ef9b25223258c131 ] + @@ -10 +11,0 @@ -Cc: stable@dpdk.org @@ -19 +20 @@ -index 4f0db21dde..ab9498a91e 100644 +index 8f7b285271..5d2ffe416c 100644 @@ -22 +23 @@ -@@ -404,6 +404,8 @@ Limitations +@@ -226,6 +226,8 @@ Limitations @@ -28,2 +29,2 @@ - - LRO can be used with outer header of TCP packets of the standard format: - eth (with or without vlan) / ipv4 or ipv6 / tcp / payload + + - Timestamps: