From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2 4/8] eal: fix hotplug add / remove Date: Wed, 12 Jul 2017 00:18:35 +0200 Message-ID: <5976076.1A8C0d6yF4@xps> References: <5f9ae5a1d9230c96cf7edeff89cc316523732747.1499728330.git.gaetan.rivet@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Gaetan Rivet Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id E433E2C54 for ; Wed, 12 Jul 2017 00:18:36 +0200 (CEST) In-Reply-To: <5f9ae5a1d9230c96cf7edeff89cc316523732747.1499728330.git.gaetan.rivet@6wind.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" 11/07/2017 01:19, Gaetan Rivet: > New device should be represented by an rte_devargs prior to being > plugged. Why this assumption? Please start by stated the issue to solve. > Device parameters are available to rte_devices via their devargs field. > This field should be set up as soon as possible, as central information > are stored within, such as the device name which is used to search > the newly scanned device before plugging it in. > > When a device is introduced using the hotplug API, it is implicitly > whitelisted. As such, it can conflict with existing bus configuration. > The new rte_devargs uses the new rte_eal_devargs_insert function that > supersedes previous rte_devargs, allowing to force the insertion of new > devices. I cannot parse this sentence. I probably need to sleep and read it again ;)