From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [RFC PATCH] eal:Add new API for parsing args at rte_eal_init time Date: Thu, 4 Jun 2015 07:47:04 -0700 Message-ID: <20150604074704.2ce0514b@urahara> References: <1433357393-54434-1-git-send-email-keith.wiles@intel.com> <20150603171255.545e0df8@urahara> <20150604135542.GC24585@hmsreliant.think-freely.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "dev@dpdk.org" To: Neil Horman Return-path: Received: from mail-qk0-f174.google.com (mail-qk0-f174.google.com [209.85.220.174]) by dpdk.org (Postfix) with ESMTP id E506DC33E for ; Thu, 4 Jun 2015 16:47:04 +0200 (CEST) Received: by qkx62 with SMTP id 62so24863965qkx.3 for ; Thu, 04 Jun 2015 07:47:04 -0700 (PDT) In-Reply-To: <20150604135542.GC24585@hmsreliant.think-freely.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, 4 Jun 2015 09:55:42 -0400 Neil Horman wrote: > That said, I'm not sure theres much value in adding this to the API. For one, > it implies that dpdk arguments need to come first on the command line. While > all the example applications do that, theres no requirement that they do so, and > this function silently implies that they have to, so any existing applications > in the wild that violate that assumption are enjoined from using this I found that the only way to support daemon command line args is to put local arguments first, then call EAL to parse it's args.