From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id F31DC206C9; Tue, 4 Jul 2017 20:00:25 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 04 Jul 2017 20:00:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=qI9F4SqKU7HICSV TOtYC64XzcDVKKnmQU+3c98V3AJE=; b=TVkvpkcZEVQrebVC39DXs2oyRIy+tNL rvL6+FtJoL9dnYGL/xmPhoDCHIbjj6Oro17hm85+Q+mPERggD4k0eYxLEwCQaW74 R0iaEo/K7FPbu8aJPW999joTlkZGv8dmSZ3OW9tiQ3ryF9ozm79DwIBWUufkS32F +qrQKPeclWYE= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=qI9F4SqKU7HICSVTOtYC64XzcDVKKnmQU+3c98V3AJE=; b=V//an7wg twUIb4b/2euuQlDz/+k8zPXxhdvtckDFqhJDUYrjXMg9F9mg5cxlYgofbT5dfgdX k4YNDHGox3vKvo6WmSvW+00Trva0aFzVULFSMi4XR3xnwojLCZuRHJc4G6PVR1x5 lYQYNxI5kHa1nKZ2fPPuJ4B0lCePgGogKmVkVjSUtBsFexCzElDYpQ10eg2DmZxi Dt4yCS/Xfmj7Ta/GI8YZZjfqDC7Fe8PNYR5WMsuVPlEsmMRnQz4NpbV4BAqHNROT HCFS7WLI8gUFhXG8+nA9EjMVHCjhmVnAnf89UJ/b+UqKqR2FsBC3Z0nW7qLvuUlf /Fm8SpcfAWydPQ== X-ME-Sender: X-Sasl-enc: rV3ejh5fZPqayjKZXDQPgMh41s7PurCt3y9TyDMXP70q 1499212825 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id AEE9624251; Tue, 4 Jul 2017 20:00:25 -0400 (EDT) From: Thomas Monjalon To: Jacek Piasecki , bruce.richardson@intel.com Cc: dev@dpdk.org, deepak.k.jain@intel.com Date: Wed, 05 Jul 2017 02:00:24 +0200 Message-ID: <1705823.nvDJz8A6NC@xps> In-Reply-To: <1498560760-104196-1-git-send-email-jacekx.piasecki@intel.com> 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-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3 0/3] EAL change for using a config file for DPDK X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2017 00:00:26 -0000 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.