From: Thomas Monjalon <thomas@monjalon.net>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] doc: add link to mbuf layout history
Date: Mon, 11 May 2026 15:00:36 +0200 [thread overview]
Message-ID: <MytLSAGsRfqGQpE8fyv5ow@monjalon.net> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35F657D8@smartserver.smartshare.dk>
07/04/2026 10:44, Morten Brørup:
> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > Sent: Tuesday, 7 April 2026 10.06
> >
> > In order to illustrate how mbuf is kept small,
> > add a link to a page showing the mbuf layout for each version.
> >
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > ---
> > doc/guides/prog_guide/mbuf_lib.rst | 11 ++++++-----
> > 1 file changed, 6 insertions(+), 5 deletions(-)
> >
> > diff --git a/doc/guides/prog_guide/mbuf_lib.rst
> > b/doc/guides/prog_guide/mbuf_lib.rst
> > index 382bfbdca4..97f8e72356 100644
> > --- a/doc/guides/prog_guide/mbuf_lib.rst
> > +++ b/doc/guides/prog_guide/mbuf_lib.rst
> > @@ -8,11 +8,12 @@ The Packet (MBuf) library provides the ability to
> > allocate and free buffers (mbu
> > that may be used by the DPDK application to store message buffers.
> > The message buffers are stored in a mempool, using the
> > :doc:`mempool_lib`.
> >
> > -A rte_mbuf struct generally carries network packet buffers, but it can
> > actually
> > -be any data (control data, events, ...).
> > -The rte_mbuf header structure is kept as small as possible and
> > currently uses
> > -just two cache lines, with the most frequently used fields being on
> > the first
> > -of the two cache lines.
> > +A ``struct rte_mbuf`` generally carries network packet buffers,
> > +but it can actually be any data (control data, events, etc).
> > +The ``rte_mbuf`` header structure is
> > +`kept as small as possible
> > <https://doc.dpdk.org/struct/mbuf/history.html>`_
> > +and currently uses just two 64-byte cache lines,
> > +with the most frequently used fields being on the first of the two
> > cache lines.
> >
> > Design of Packet Buffers
> > ------------------------
> > --
> > 2.53.0
>
> Hadn't noticed that illustration before, so good idea linking to it here.
>
> Acked-by: Morten Brørup <mb@smartsharesystems.com>
Applied
prev parent reply other threads:[~2026-05-11 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 8:05 [PATCH] doc: add link to mbuf layout history Thomas Monjalon
2026-04-07 8:44 ` Morten Brørup
2026-04-07 10:35 ` Thomas Monjalon
2026-05-11 13:00 ` Thomas Monjalon [this message]
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=MytLSAGsRfqGQpE8fyv5ow@monjalon.net \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
/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