From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 7766020615; Tue, 11 Jul 2017 18:18:36 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 11 Jul 2017 18:18:36 -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=6wLm5ed1XRhhOFf o/gNnPb1oxAUQ3lLDsh5/vxMD8EA=; b=P3EHvZkE2AGjgE/63QBirD5w42cWsEM J4epbpI4g3wCHHB4omx5MvQPgtCtJwew3AgkETQkDS016OBiDxprOD9GYIxWoot1 6WOTZNlvaIuuVFCpwatplEIJwoCi/SuVxluogrkZDjJBOstQo/8bSFEz4B2WPboz 95SpqDJ7FXRQ= 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=6wLm5ed1XRhhOFfo/gNnPb1oxAUQ3lLDsh5/vxMD8EA=; b=Sm7RNzhg 5TDlR8kXUl4UOV4O2k9aV97+bbuHDB9AJOXhk1TuQPZlSMGmmbbRcp2BEZU1BeXB afNSe1u/5HMK39BkuBfUcz9CDKxqWO0KhGXckbr9PrpOCAKzJEMt6NB9PVpGPnjL PNfm4n8UlXJ0l+WEoTddhlRXGmZCLcHfD3rerplFeLS+acp6ujNySL9GM/x664on uAvJqrTcPvIpqfRgoedjSe1iM2O0mTyp1Sj4w5ybP1h4jYiWURRV+xuqHndPptII m4LpKPv2FrGCegyqTl6ywP++CUxEXdOGoPSF3rZS6iJzDdpyOfJzlFODZmRfLIA/ jdD+sLNPsEQvJQ== X-ME-Sender: X-Sasl-enc: nFh1OHZoliEjbq/Xd21fuIOw4RZRqpG9xXGZA8V2tXGQ 1499811516 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 30AFE2424F; Tue, 11 Jul 2017 18:18:36 -0400 (EDT) From: Thomas Monjalon To: Gaetan Rivet Cc: dev@dpdk.org Date: Wed, 12 Jul 2017 00:18:35 +0200 Message-ID: <5976076.1A8C0d6yF4@xps> In-Reply-To: <5f9ae5a1d9230c96cf7edeff89cc316523732747.1499728330.git.gaetan.rivet@6wind.com> References: <5f9ae5a1d9230c96cf7edeff89cc316523732747.1499728330.git.gaetan.rivet@6wind.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2 4/8] eal: fix hotplug add / remove 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: Tue, 11 Jul 2017 22:18:37 -0000 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 ;)