From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Morten Brørup" <mb@smartsharesystems.com>,
"Olivier Matz" <olivier.matz@6wind.com>
Cc: dev@dpdk.org, Konstantin Ananyev <konstantin.ananyev@intel.com>,
Jiayu Hu <jiayu.hu@intel.com>
Subject: Re: [dpdk-dev] RTE prefix on more libs
Date: Mon, 24 Jun 2019 17:39:49 +0100 [thread overview]
Message-ID: <d05413be-f1cc-baa4-0491-32ce20f68dbb@intel.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35B42968@smartserver.smartshare.dk>
On 6/21/2019 12:29 PM, Morten Brørup wrote:
> Hi Olivier and Ferruh,
>
>
>
> I haven’t followed the discussions about adding the RTE prefix in details. Was
> there a conclusion about adding the RTE prefix in public identifiers of other
> (core) libraries, e.g. the IP Fragmentation and GRO/GSO libraries?
>
>
>
> Or was it concluded that only the Network Headers library (librte_net) should be
> updated, arguing that conflicts with standard O/S library headers were mainly
> here, and the ripple effect of more widespread changes would be too costly for
> consumers of DPDK?
As far as I remember we have not explicitly state to update or not update all
public headers, the discussion was mainly about the conflicts,
we can discuss to update all public headers but because of the reasons you
mentioned above, I am not for changing public headers if they don't cause any
conflict.
prev parent reply other threads:[~2019-06-24 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 11:29 Morten Brørup
2019-06-24 16:39 ` Ferruh Yigit [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=d05413be-f1cc-baa4-0491-32ce20f68dbb@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jiayu.hu@intel.com \
--cc=konstantin.ananyev@intel.com \
--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).