From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v3 0/3] EAL change for using a config file for DPDK Date: Wed, 05 Jul 2017 02:00:24 +0200 Message-ID: <1705823.nvDJz8A6NC@xps> References: <1498474759-102089-6-git-send-email-jacekx.piasecki@intel.com> <1498560760-104196-1-git-send-email-jacekx.piasecki@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, deepak.k.jain@intel.com To: Jacek Piasecki , bruce.richardson@intel.com Return-path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 963F64C57 for ; Wed, 5 Jul 2017 02:00:26 +0200 (CEST) In-Reply-To: <1498560760-104196-1-git-send-email-jacekx.piasecki@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 27/06/2017 12:52, Jacek Piasecki: > This patchset introduce a mechanism for running dpdk application with parameters > provided by configuration file. > > A new API for EAL takes a config file data type - either loaded from file, > or built up programmatically in the application - and extracts DPDK parameters > from it to be used when eal init is called. This allows apps to have > an alternative method to configure EAL, other than via command-line parameters. I think we should focus on better API for apps instead of forging the default EAL config into the stone of a config file. Anyway, we do not have enough time in 17.08 release cycle to properly discuss this important topic. I hope it opens the discussion in order to have a clear view of what we could change and integrate in 17.11.