From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Olivier Matz" <olivier.matz@6wind.com>,
"Ferruh Yigit" <ferruh.yigit@intel.com>
Cc: <dev@dpdk.org>,
"Konstantin Ananyev" <konstantin.ananyev@intel.com>,
"Jiayu Hu" <jiayu.hu@intel.com>
Subject: [dpdk-dev] RTE prefix on more libs
Date: Fri, 21 Jun 2019 13:29:26 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35B42968@smartserver.smartshare.dk> (raw)
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?
Med venlig hilsen / kind regards
Morten Brørup
CTO
SmartShare Systems A/S
Tonsbakken 16-18
DK-2740 Skovlunde
Denmark
Office +45 70 20 00 93
Direct +45 89 93 50 22
Mobile +45 25 40 82 12
mb@smartsharesystems.com <mailto:mb@smartsharesystems.com>
www.smartsharesystems.com <https://www.smartsharesystems.com/>
next reply other threads:[~2019-06-21 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 11:29 Morten Brørup [this message]
2019-06-24 16:39 ` Ferruh Yigit
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=98CBD80474FA8B44BF855DF32C47DC35B42968@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jiayu.hu@intel.com \
--cc=konstantin.ananyev@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).