From: John Guzik <john@shieldxnetworks.com>
To: dev@dpdk.org
Cc: John Guzik <john@shieldxnetworks.com>
Subject: [PATCH] doc: Programmers guide IP fragmentation direct/indirect mbufs to wrong section
Date: Mon, 11 Apr 2016 11:24:47 -0700 [thread overview]
Message-ID: <1460399087-23904-1-git-send-email-john@shieldxnetworks.com> (raw)
---
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
next reply other threads:[~2016-04-11 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 18:24 John Guzik [this message]
2016-04-11 18:57 ` [PATCH] doc: Programmers guide IP fragmentation direct/indirect mbufs to wrong section Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1460399087-23904-1-git-send-email-john@shieldxnetworks.com \
--to=john@shieldxnetworks.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).