DPDK patches and discussions
 help / color / mirror / Atom feed
From: Antti Kantee <pooka@fixup.fi>
To: Thomas Monjalon <thomas.monjalon@6wind.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] symbol conflicts between netinet/in.h, arpa/inet.h, and rte_ip.h
Date: Fri, 25 Jul 2014 14:40:02 +0000	[thread overview]
Message-ID: <53D26C42.3060907@fixup.fi> (raw)
In-Reply-To: <1432797.FfhxlLyX1P@xps13>

On 25/07/14 10:43, Thomas Monjalon wrote:
>> On 24/07/14 07:59, Matthew Hall wrote:
>>> I ran into some weird symbol conflicts between system netinet/in.h and DPDK
>>> rte_ip.h. They have a lot of duplicated definitions for stuff like IPPROTO_IP
>>> and so on. This breaks when you want to use inet_pton from arpa/inet.h,
>>> because it includes netinet/in.h to define struct in_addr.
> [...]
>> Again, I recommend steering away from any tightrope approaches that
>> "know" which types are non-conflicting, or pick out half-and-half from
>> the host and IP stack.  "Do, or do not, there is no half-and-half"
>
> The general problem here is that DPDK is conflicting with libc.
> So the obvious question would be: "why DPDK needs to redefine libc stuff"?
> I don't see any obvious answer since bare metal is planned to be removed.
> (see http://dpdk.org/ml/archives/dev/2014-June/003868.html)

One reason is if you want DPDK to be a portable network programming 
environment.  Especially in that case you do not want definitions based 
on hackish assumptions of some particular version of some particular 
host implementation.  However, I'm not trying to argue if DPDK should or 
shouldn't be that, just that you should either dramatically improve the 
current implementation or nuke it.

      reply	other threads:[~2014-07-25 14:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24  7:59 Matthew Hall
2014-07-24 15:43 ` Niraj Sharma (nirajsha)
2014-07-24 22:55 ` Antti Kantee
2014-07-24 23:03   ` Matthew Hall
2014-07-25  1:12   ` Wu, Jingjing
2014-07-25  4:56     ` Matthew Hall
2014-07-25 10:33       ` Ananyev, Konstantin
2014-07-25 10:43   ` Thomas Monjalon
2014-07-25 14:40     ` Antti Kantee [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=53D26C42.3060907@fixup.fi \
    --to=pooka@fixup.fi \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@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).