From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: A.McLoughlin <aideen.mcloughlin@intel.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
Olivier Matz <olivier.matz@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"harry.van.haaren@intel.com" <harry.van.haaren@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add graphic showing layout of mbuf struct
Date: Sat, 24 Aug 2019 12:18:05 +0000 [thread overview]
Message-ID: <BYAPR18MB2424B5806C4B19C10EF4C39AC8A70@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20190823131007.9000-1-aideen.mcloughlin@intel.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of A.McLoughlin
> Sent: Friday, August 23, 2019 6:40 PM
> To: John McNamara <john.mcnamara@intel.com>; Marko Kovacevic
> <marko.kovacevic@intel.com>; Olivier Matz <olivier.matz@6wind.com>
> Cc: dev@dpdk.org; harry.van.haaren@intel.com; A.McLoughlin
> <aideen.mcloughlin@intel.com>
> Subject: [dpdk-dev] [PATCH] doc: add graphic showing layout of mbuf struct
>
> 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>
> ---
> doc/guides/prog_guide/img/mbuf_graphic.svg | 7285 ++++++++++++++++++++
> doc/guides/prog_guide/mbuf_lib.rst | 9 +
> 2 files changed, 7294 insertions(+)
> create mode 100644 doc/guides/prog_guide/img/mbuf_graphic.svg
The diagram shows uint16_t refcnt(+atomic). I think, +atomic is not need here.
next prev parent reply other threads:[~2019-08-24 12:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 13:10 A.McLoughlin
2019-08-24 12:18 ` Jerin Jacob Kollanukkaran [this message]
2019-08-27 9:02 ` [dpdk-dev] [PATCH v3] " A.McLoughlin
2019-10-17 15:58 ` Olivier Matz
2019-10-18 10:56 ` Jerin Jacob
2020-05-24 21:24 ` 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=BYAPR18MB2424B5806C4B19C10EF4C39AC8A70@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=aideen.mcloughlin@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.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 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).