From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id CD3B74381C; Fri, 5 Jan 2024 03:57:19 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 52C5C402AC; Fri, 5 Jan 2024 03:57:19 +0100 (CET) Received: from mgamail.intel.com (mgamail.intel.com [134.134.136.20]) by mails.dpdk.org (Postfix) with ESMTP id 2C7574027C for <dev@dpdk.org>; Fri, 5 Jan 2024 03:57:16 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1704423437; x=1735959437; h=from:to:cc:subject:date:message-id; bh=M92Rl9ic/7MLR9TR8xD2SMuj1xoMt+X7fabZSLMHwKc=; b=Dezci6ayRvLLjo+Kxn8NvQq/P9drbl/Hfm+70J0up3jhfpA/XrsGPBp9 U9lr3+v329x3gQ9P2Yhvg+CXTK4p4NAiZDa6/QHWK2MdecyzOnmVk/sJ5 hXXd3DCCWKWxFuQSTmT+6Ijy5DYFSupOFZbzGlujXM67rxskJxK7eeqU8 A/PVExn6+ai4HCnVIjobRo258OLykBOpoFEHcK7DmD91e+uP8W4oR0Bhh n7uTCMlvaZq9kP334uZXVTzSU4xCbUBXnJ3b5Djr3gKZ7PTEg64Fh1nOg 5DMBocrygBfyIMj0pEXFxDUB1IG3EEfVKImqsI3dTI+NZJNGxC8ImcZZu g==; X-IronPort-AV: E=McAfee;i="6600,9927,10943"; a="387870485" X-IronPort-AV: E=Sophos;i="6.04,332,1695711600"; d="scan'208";a="387870485" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Jan 2024 18:56:59 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10943"; a="904035168" X-IronPort-AV: E=Sophos;i="6.04,332,1695711600"; d="scan'208";a="904035168" Received: from unknown (HELO npg-dpdk-simeisu-cvl-119d218.sh.intel.com) ([10.67.119.108]) by orsmga004.jf.intel.com with ESMTP; 04 Jan 2024 18:56:57 -0800 From: Simei Su <simei.su@intel.com> To: konstantin.v.ananyev@yandex.ru Cc: dev@dpdk.org, qi.z.zhang@intel.com, qiming.yang@intel.com, Simei Su <simei.su@intel.com> Subject: [PATCH] doc: update default value for config parameter Date: Fri, 5 Jan 2024 10:44:17 +0800 Message-Id: <20240105024417.77843-1-simei.su@intel.com> X-Mailer: git-send-email 2.9.5 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Update documentation value to match default value in code base. Signed-off-by: Simei Su <simei.su@intel.com> --- 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 314d4ad..b14289e 100644 --- a/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst +++ b/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst @@ -43,7 +43,7 @@ Note that all update/lookup operations on Fragment Table are not thread safe. So if different execution contexts (threads/processes) will access the same table simultaneously, 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.9.5