From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Guzik Subject: [PATCH] doc: Programmers guide IP fragmentation direct/indirect mbufs to wrong section Date: Mon, 11 Apr 2016 11:24:47 -0700 Message-ID: <1460399087-23904-1-git-send-email-john@shieldxnetworks.com> Cc: John Guzik To: dev@dpdk.org Return-path: Received: from net-apps-01.shieldx.dev (unknown [50.242.104.1]) by dpdk.org (Postfix) with ESMTP id AC4DD2949 for ; Mon, 11 Apr 2016 20:24:45 +0200 (CEST) List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" --- 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 1d3d4ac..196d93c 100644 --- a/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst +++ b/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst @@ -54,7 +54,7 @@ Finally 'direct' and 'indirect' mbufs for each fragment are linked together via The caller has an ability to explicitly specify which mempools should be used to allocate 'direct' and 'indirect' mbufs from. -For more information about direct and indirect mbufs, refer to the *DPDK Programmers guide 7.7 Direct and Indirect Buffers.* +For more information about direct and indirect mbufs, refer to the *DPDK Programmers guide 6.7 Direct and Indirect Buffers.* Packet reassembly ----------------- -- 1.9.1