From 85c05b5147a31e9a4758a1cdf6b5664bf554eac4 Mon Sep 17 00:00:00 2001 From: Baruch Siach Date: Tue, 6 Dec 2016 10:25:25 +0200 Subject: [PATCH] doc: fix description of attach to indirect mbuf Since commit 4a96e8b652181 ("mbuf: allow to clone an indirect mbuf") attaching to an indirect mbuf creates a clone of that mbuf. Update the mbuf documentation to match. Signed-off-by: Baruch Siach Acked-by: John McNamara --- doc/guides/prog_guide/mbuf_lib.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/guides/prog_guide/mbuf_lib.rst b/doc/guides/prog_guide/mbuf_lib.rst index f0aa21a6d4..6e73fc5a83 100644 --- a/doc/guides/prog_guide/mbuf_lib.rst +++ b/doc/guides/prog_guide/mbuf_lib.rst @@ -253,7 +253,8 @@ Similarly, whenever the indirect buffer is detached, the reference counter on th If the resulting reference counter is equal to 0, the direct buffer is freed since it is no longer in use. There are a few things to remember when dealing with indirect buffers. -First of all, it is not possible to attach an indirect buffer to another indirect buffer. +First of all, an indirect buffer is never attached to another indirect buffer. +Attempting to attach buffer A to indirect buffer B that is attached to C, makes rte_pktmbuf_attach() automatically attach A to C, effectively cloning B. Secondly, for a buffer to become indirect, its reference counter must be equal to 1, that is, it must not be already referenced by another indirect buffer. Finally, it is not possible to reattach an indirect buffer to the direct buffer (unless it is detached first). -- 2.20.1