From: Thomas Monjalon <thomas@monjalon.net>
To: "Kinsella, Ray" <mdr@ashroe.eu>
Cc: dev@dpdk.org, olivier.matz@6wind.com,
Neil Horman <nhorman@tuxdriver.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
david.marchand@redhat.com, arybchenko@solarflare.com
Subject: Re: [dpdk-dev] [PATCH] doc: announce API change in mbuf
Date: Thu, 06 Aug 2020 02:07:21 +0200 [thread overview]
Message-ID: <3176340.0iDIModgNF@thomas> (raw)
In-Reply-To: <2b245241-5e09-49c4-daf2-79803788615d@ashroe.eu>
05/08/2020 11:28, Kinsella, Ray:
>
> On 31/07/2020 17:03, Thomas Monjalon wrote:
> > In order to prepare for adding more features requiring more space in mbuf,
> > some static fields must become dynamic.
> > Some small layout changes may have performance benefits as well.
> >
> > The deprecation notice for atomic refcount is moved and reworded
> > to fit below the layout deprecation.
> >
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > ---
>
> So what does anyone using these fields do - except panic perhaps.
> Can we include a reference to the DPDK Userspace presentation,
> in advance of the documentation supporting the dynamic mbuf.
> To prepare people for what is to come ...
>
> https://www.youtube.com/watch?v=Ttl6MlhmzWY
Good idea, link added.
Applied
next prev parent reply other threads:[~2020-08-06 0:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 16:03 [dpdk-dev] [PATCH] doc: announce API change in mbuf Thomas Monjalon
2020-08-02 19:28 ` Olivier Matz
2020-08-03 12:43 ` Andrew Rybchenko
2020-08-03 14:25 ` David Marchand
2020-08-05 9:28 ` Kinsella, Ray
2020-08-06 0:07 ` Thomas Monjalon [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-01 12:41 Thomas Monjalon
2019-08-04 21:33 ` Olivier Matz
2019-08-05 8:05 ` Andrew Rybchenko
2019-08-05 10:14 ` 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=3176340.0iDIModgNF@thomas \
--to=thomas@monjalon.net \
--cc=arybchenko@solarflare.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=mdr@ashroe.eu \
--cc=nhorman@tuxdriver.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.