From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Hall Subject: Re: symbol conflicts between netinet/in.h, arpa/inet.h, and rte_ip.h Date: Thu, 24 Jul 2014 16:03:27 -0700 Message-ID: <20140724230327.GA26512@mhcomputing.net> References: <20140724075918.GA21277@mhcomputing.net> <53D18EFF.8080804@fixup.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "dev-VfR2kkLFssw@public.gmane.org" To: Antti Kantee Return-path: Content-Disposition: inline In-Reply-To: <53D18EFF.8080804-jIVgJlTk8bs@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" 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.