From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Jan Viktorin <viktorin@rehivetech.com>
Cc: dev <dev@dpdk.org>, Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] doc: announce renaming of ethdev library
Date: Thu, 28 Jul 2016 11:29:53 +0200 [thread overview]
Message-ID: <CAATJJ0J8FdgFf5fu==kOjiy-quvA4W3uCrwGHASVBt3Kau78Eg@mail.gmail.com> (raw)
In-Reply-To: <20160727183308.2c2efcf7@pcviktorin.fit.vutbr.cz>
Hi Thomas,
just my two cents as Ubuntu DPDK maintainer (and part of the Debian Team
that does the same).
(Yeah I really could reuse it three times :-) )
It will be a bit of effort to adapt, but should be no rocket-science.
I like that eventually the namespace will be cleaner.
Just curious, do we already know by looking ahead if ethdev will get an ABI
bump anyway?
So will the transition be:
a) libethdev4 -> librte_ethdev5
b)libethdev4 -> librte_ethdev4
If it is b) would/should one provide a compat symlink then in your Opinion?
Anyway, for now I think it is fair to say:
Acked-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
On Wed, Jul 27, 2016 at 6:33 PM, Jan Viktorin <viktorin@rehivetech.com>
wrote:
> On Tue, 26 Jul 2016 18:22:21 +0200
> Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
>
> > The right name of ethdev should be dpdk_netdev. However:
> > 1/ We are using rte_ prefix in the code and library names.
> > 2/ The API uses rte_ethdev
> > That's why 16.11 will just have the rte_ prefix prepended to
> > the library filename as every other libraries.
> >
> > Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> >
> Acked-by: Jan Viktorin <viktorin@rehivetech.com>
>
next prev parent reply other threads:[~2016-07-28 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 16:22 [dpdk-dev] [PATCH] " Thomas Monjalon
2016-07-27 16:33 ` [dpdk-dev] " Jan Viktorin
2016-07-28 9:29 ` Christian Ehrhardt [this message]
2016-07-28 9:52 ` Thomas Monjalon
2016-07-28 17:37 ` Thomas Monjalon
[not found] ` <B27915DBBA3421428155699D51E4CFE2025A902D@IRSMSX103.ger.corp.intel.com>
[not found] ` <2601191342CEEE43887BDE71AB97725836B8AAA2@irsmsx105.ger.corp.intel.com>
[not found] ` <B27915DBBA3421428155699D51E4CFE2025A9104@IRSMSX103.ger.corp.intel.com>
2016-07-28 11:29 ` [dpdk-dev] [PATCH] " Ananyev, Konstantin
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='CAATJJ0J8FdgFf5fu==kOjiy-quvA4W3uCrwGHASVBt3Kau78Eg@mail.gmail.com' \
--to=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--cc=viktorin@rehivetech.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).