From: Matthew Hall <mhall@mhcomputing.net>
To: Antti Kantee <pooka@fixup.fi>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] symbol conflicts between netinet/in.h, arpa/inet.h, and rte_ip.h
Date: Thu, 24 Jul 2014 16:03:27 -0700 [thread overview]
Message-ID: <20140724230327.GA26512@mhcomputing.net> (raw)
In-Reply-To: <53D18EFF.8080804@fixup.fi>
On Thu, Jul 24, 2014 at 10:55:59PM +0000, Antti Kantee wrote:
> In my experience from years of fighting with more or less this exact same
> problem -- the fight is now thankfully over but the scars remain -- you
> either want to expose a complete set of types and provide support for
> everything, or you want to expose nothing.
I don't have a problem with this approach. Implementing it would require the
DPDK to create user accessible functions for creating MAC addresses, IPs,
CIDRs, and TCP / UDP port numbers. Many of the things required are hiding
inside of *cmdline* code where it's impossible for anybody to access them.
Matthew.
next prev parent reply other threads:[~2014-07-24 23:02 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 [this message]
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
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=20140724230327.GA26512@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=pooka@fixup.fi \
/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).