From: Thomas Monjalon <thomas@monjalon.net>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: Olivier Matz <olivier.matz@6wind.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] The mbuf API needs some cleaning up
Date: Mon, 03 Aug 2020 12:41:27 +0200 [thread overview]
Message-ID: <4177727.sTLgoBS7LP@thomas> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35C61182@smartserver.smartshare.dk>
03/08/2020 10:42, Morten Brørup:
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Olivier Matz
> > Sent: Friday, July 31, 2020 5:25 PM
> >
> > Hi Morten,
> >
> > Thanks for the feedback.
> >
> > On Mon, Jul 13, 2020 at 11:57:38AM +0200, Morten Brørup wrote:
> >
> > > The MBUF library exposes some macros and constants without the RTE_
> > prefix. I
> > > propose cleaning up these, so better names get into the coming LTS
> > release.
> >
> > Yes, Thomas talked about it some time ago and he even drafted a patch
> > to
> > fix it. We can target 20.11 for the changes, but I think we'll have to
> > keep a compat API until 21.11.
> >
>
> Great, then I will back off. No need for multiple patches fixing the same things. :-)
Morten, you are very welcome to work on cleaning mbuf API.
I think we must focus on introducing the new names,
while keeping old names as alias for one year.
The other things to do is to provide a devtools script
to help converting applications to the new names.
prev parent reply other threads:[~2020-08-03 10:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 9:57 Morten Brørup
2020-07-31 15:24 ` Olivier Matz
2020-08-03 8:42 ` Morten Brørup
2020-08-03 10:41 ` 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=4177727.sTLgoBS7LP@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.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).