[dpdk-dev] [PATCH] doc: Programmers guide IP fragmentation direct/indirect mbufs to wrong section
2016-04-11 11:24, John Guzik: > --- a/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst > +++ b/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst > -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.* We should replace it by a link. There are some remaining hard references in the docs: doc/guides/nics/virtio.rst: For more details about kni, please refer to Chapter 24 "Kernel NIC Interface". doc/guides/prog_guide/ip_fragment_reassembly_lib.rst: For more information about direct and indirect mbufs, refer to the *DPDK Programmers guide 7.7 Direct and Indirect Buffers.* doc/guides/sample_app_ug/multi_process.rst: (refer to *DPDK Programmer's Guide* , Section 6.4, "Local Cache")
[dpdk-dev] [PATCH] doc: Programmers guide IP fragmentation direct/indirect mbufs to wrong section
--- 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
