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 329CB43DF8 for ; Thu, 4 Apr 2024 11:52:42 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2D1A2402D8; Thu, 4 Apr 2024 11:52:42 +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 D30D740648 for ; Thu, 4 Apr 2024 11:52:40 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1712224360; 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=SNe/QIflMqp2jfn3cghUslUwVRbx1gu4UOg2+7HwcKA=; b=W8pSEXY4XT3bF81hA7MEWnteHd3KMVCp4Fv+CyavA9ZvC4xbp61kmx3K6lgmDWQjmnzDcK aEaI4mwFSQMYTRge11901oC4ygoBWiyrn/YSCvERvqdSGjD0qwm+qvSm0d32SNYiEx4NiU vYyR1FZQnbgnDOQd/IwiJXc6kNSpAPs= Received: from mimecast-mx02.redhat.com (mx-ext.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-264-Uo-QcFjTP76yS3zv9_sj3A-1; Thu, 04 Apr 2024 05:52:39 -0400 X-MC-Unique: Uo-QcFjTP76yS3zv9_sj3A-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (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 mimecast-mx02.redhat.com (Postfix) with ESMTPS id B35D91C05EA4; Thu, 4 Apr 2024 09:52:38 +0000 (UTC) Received: from rh.Home (unknown [10.39.192.22]) by smtp.corp.redhat.com (Postfix) with ESMTP id 0EFEA3C85; Thu, 4 Apr 2024 09:52:37 +0000 (UTC) From: Kevin Traynor To: Simei Su Cc: Tyler Retzlaff , dpdk stable Subject: patch 'doc: fix default IP fragments maximum in programmer guide' has been queued to stable release 21.11.7 Date: Thu, 4 Apr 2024 10:51:44 +0100 Message-ID: <20240404095155.155427-14-ktraynor@redhat.com> In-Reply-To: <20240404095155.155427-1-ktraynor@redhat.com> References: <20240404095155.155427-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.1 X-Mimecast-Spam-Score: 0 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.7 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 04/09/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/46f9124cae76db161f2670fd22a4cf0ae9c37661 Thanks. Kevin --- >From 46f9124cae76db161f2670fd22a4cf0ae9c37661 Mon Sep 17 00:00:00 2001 From: Simei Su Date: Fri, 5 Jan 2024 10:44:17 +0800 Subject: [PATCH] doc: fix default IP fragments maximum in programmer guide [ upstream commit 0219d467bcb1d19b386b5bae8eecd3514ba13fdb ] Update documentation value to match default value in code base. Fixes: f8e0f8ce9030 ("ip_frag: increase default maximum of fragments") Signed-off-by: Simei Su Acked-by: Tyler Retzlaff --- doc/guides/prog_guide/ip_fragment_reassembly_lib.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst b/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst index 314d4adbb8..b14289eb73 100644 --- a/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst +++ b/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst @@ -44,5 +44,5 @@ So if different execution contexts (threads/processes) will access the same tabl then some external syncing mechanism have to be provided. -Each table entry can hold information about packets consisting of up to RTE_LIBRTE_IP_FRAG_MAX (by default: 4) fragments. +Each table entry can hold information about packets consisting of up to RTE_LIBRTE_IP_FRAG_MAX (by default: 8) fragments. Code example, that demonstrates creation of a new Fragment table: -- 2.44.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2024-04-04 10:49:34.372936234 +0100 +++ 0014-doc-fix-default-IP-fragments-maximum-in-programmer-g.patch 2024-04-04 10:49:33.753457746 +0100 @@ -1 +1 @@ -From 0219d467bcb1d19b386b5bae8eecd3514ba13fdb Mon Sep 17 00:00:00 2001 +From 46f9124cae76db161f2670fd22a4cf0ae9c37661 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit 0219d467bcb1d19b386b5bae8eecd3514ba13fdb ] + @@ -9 +10,0 @@ -Cc: stable@dpdk.org