From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 037202BAA for ; Thu, 13 Jul 2017 22:48:38 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 9BC5720963; Thu, 13 Jul 2017 16:48:35 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 13 Jul 2017 16:48:35 -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=NNiprusKX23Z3/X p6h0PePyOdmWIpaQaJysKBFz7HRo=; b=XldjsQJvlCWOpzyoMxVBXv4UDzHk4k1 tI144QJ9tTYLiOK366wGDP3c+sYWTUvNoLzq8w5Dz58HxMFwi7GMh2dRibmuPIbF alLar59GuppX5+r5olXikqZHaHBgDgi/wI0NjISEB9+yl26YuupBtPXpY7XEM66m J2KN+CB5Qk9E= 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=NNiprusKX23Z3/Xp6h0PePyOdmWIpaQaJysKBFz7HRo=; b=Y3ZE1orR HMjYWHKp5j9WkHNzcGkbTrGEVR7EfV8anGZNIeG9Evjn2uc+m1REWtEp9xuVIuD2 ZVTSviLCl/SouzQpw6xxTdCskB+ARRomGnhjaX+jYq1qDa/Xfc72ml7xh2K26f+0 Jel+bNSHWfbb3txS4rrBXBG3WfldbuTvQ1uf7a7AC0B9+P/n9lXIywFeAS7OmTgE FWrQcVaXzjazal0SfpGyz7BkodgEU6Fnx66Mc8kJIKIqNXj8ULigOj5gs90L0Fh3 0lxZdyEi/LNKDvXItEVeD7PegqVs578J525uHZ2kysDGImY1Zi5tZ0C7D8xw8Qii fBOqPzkpkjS85w== X-ME-Sender: X-Sasl-enc: AAA4xeBMmX1BwcN8gFO/PAsr4su7FnH6dR/XrOvM4938 1499978915 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 4E5E57E4AA; Thu, 13 Jul 2017 16:48:35 -0400 (EDT) From: Thomas Monjalon To: jblunck@infradead.org, gaetan.rivet@6wind.com Cc: dev@dpdk.org Date: Thu, 13 Jul 2017 22:48:34 +0200 Message-ID: <6818817.jrHzc3MJ66@xps> In-Reply-To: References: <20170711232512.54641-1-jblunck@infradead.org> <20170713175900.GL11154@bidouze.vm.6wind.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Subject: Re: [dpdk-dev] [PATCH 04/13] pci: use scan_mode configuration 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: Thu, 13 Jul 2017 20:48:39 -0000 13/07/2017 21:42, Jan Blunck: > On Thu, Jul 13, 2017 at 1:59 PM, Ga=EBtan Rivet = wrote: > > On Tue, Jul 11, 2017 at 07:25:03PM -0400, Jan Blunck wrote: > >> When scanning/probing devices the bus should use its configuration ins= tead > >> of looking at the devargs->type field. > >> > > > > With this patch, how do you probe a device that was previously > > blacklisted? > > > > The answers I see to this question are pretty bad, maybe you have a good > > solution. > > > > On the other hand, can you explain why you want this limitation? What > > problem does this solve? You have one view of the hotplug API, I would > > like to understand why you hold this view. > > > > Regarding the rte_devargs API, it can be fixed without making the > > hotplug needlessly complicated I think. > > > > I must point out that the scan_mode (incorrectly named) is something > > that will be removed next release. The probe policies will be reworked > > and I don't think that the solution should be proposed as a fix a few > > days before the RC2. >=20 > You just introduced them in 17.08-rc1 and you want to remove them > again for 17.11?! Please revert these changes in this case for > 17.08-rc2. Please remember that it has been introduced to prepare the move of the bus drivers and allow some kind of hotplug as used in failsafe, without breaking the devargs syntax. This is a step in an incremental process, and experimental functions and deprecated API can be dropped for a better replacement in 17.11. > Thomas, what is your take on this? I did not change my mind: We must deprecate the syntax in devargs for 17.11. Then, with a new syntax, it will be possible to simplify a lot of things, including the probe policies. =46or now, we must work on 17.08-rc2 with two goals: - fix the API break introduced in devargs API - fix the reworked hotplug to make it work in basic PCI cases - make sure the new failsafe PMD can be integrated I will integrate only the patches which clearly fix something. Patches with justification "it would be better" will wait for 17.11. Are these rules clear enough to let us progress together in the 17.08 timeframe, and 17.11 cycle? Thanks for your efforts and making 17.08 release possible.