All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "A.McLoughlin" <aideen.mcloughlin@intel.com>,
	John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>
Cc: Olivier Matz <olivier.matz@6wind.com>,
	dev@dpdk.org, "Van Haaren, Harry" <harry.van.haaren@intel.com>,
	Jerin Jacob <jerinjacobk@gmail.com>
Subject: Re: [dpdk-dev] [PATCH v3] doc: add graphic showing layout of mbuf struct
Date: Sun, 24 May 2020 23:24:38 +0200	[thread overview]
Message-ID: <5504161.4p4Js1nEjy@thomas> (raw)
In-Reply-To: <CALBAE1OFqT90a+aLq8JY67QHFPgk62eS1X3LAccwz3mu67dDow@mail.gmail.com>

Any update?


18/10/2019 12:56, Jerin Jacob:
> On Thu, Oct 17, 2019 at 9:28 PM Olivier Matz <olivier.matz@6wind.com> wrote:
> >
> > Hi,
> >
> > On Tue, Aug 27, 2019 at 10:02:30AM +0100, A.McLoughlin wrote:
> > > This patch adds a graphical overview of the rte_mbuf struct, showing where
> > > each value is stored within the struct.
> > >
> > > Signed-off-by: A.McLoughlin <aideen.mcloughlin@intel.com>
> > > ---
> > > v1 -> v2:
> > > * changed uint16_t refcnt(+atomic) to uint16_t refcnt
> > > v2 -> v3:
> > > * added layout of extrenally stored struct rte_mbuf sched sched
> > > * added struct names for named structs
> > > * made variable names bold for differenciation from types
> > > * minor styling changes
> > > * specified that graphic represents layout on 64B machine
> > > ---
> > >  doc/guides/prog_guide/img/mbuf_graphic.svg | 6962 ++++++++++++++++++++
> > >  doc/guides/prog_guide/mbuf_lib.rst         |   12 +
> > >  2 files changed, 6974 insertions(+)
> > >  create mode 100644 doc/guides/prog_guide/img/mbuf_graphic.svg
> >
> > The diagram is nice, however we have to be careful because it
> > has to be kept sync with the code. I tried to edit the svg with
> > inkscape, and it seems the text is described as vector shapes,
> > which make the diagram impossible to update.
> >
> > Couldn't it be replaced by the output of pahole? Or better, just explain
> > how to generate it in the documentation? The user can then be sure that
> 
> +1 for explaining how to generate it in the documentation as pahole
> output varies for the 128B cache line machine.
> 
> 
> > the information is up to date, matches its architecture, and can also
> > check structures other than mbuf.





      reply	other threads:[~2020-05-24 21:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190823131007.9000-1-aideen.mcloughlin@intel.com>
2019-08-24 12:18 ` [dpdk-dev] [PATCH] doc: add graphic showing layout of mbuf struct Jerin Jacob Kollanukkaran
     [not found] ` <20190827090230.2057-1-aideen.mcloughlin@intel.com>
2019-10-17 15:58   ` [dpdk-dev] [PATCH v3] " Olivier Matz
2019-10-18 10:56     ` Jerin Jacob
2020-05-24 21:24       ` 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=5504161.4p4Js1nEjy@thomas \
    --to=thomas@monjalon.net \
    --cc=aideen.mcloughlin@intel.com \
    --cc=dev@dpdk.org \
    --cc=harry.van.haaren@intel.com \
    --cc=jerinjacobk@gmail.com \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=olivier.matz@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.