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 21ED62030; Wed, 13 Dec 2017 22:20:53 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 9FEF820B56; Wed, 13 Dec 2017 16:20:52 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 13 Dec 2017 16:20:52 -0500 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; s=mesmtp; bh=tFzthUFD1UViUgmtbwpwrc/2PJ cyfacskLIIVO7Yc+I=; b=YpWuEuegvoVB/W0J//JfW01VAg50WWtwXxo53Xsfru z3C3r7pNWA8FK1Hin7fWLV42C4caifdWboBA9e2gpX7GX4l/HLhlJH1f8rKMhWRx DUqv/RTJ8QgVPaXcBMVpNgMFAs2xk7l6UMRKyDJbVuEzSxnkWARcmYZR9iHY7Y56 0= 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; s=fm1; bh=tFzthU FD1UViUgmtbwpwrc/2PJcyfacskLIIVO7Yc+I=; b=Z/WMoQwFSzH5csdBs56v9Y P0x20Vs8UPv11RmAou0BOIkbVx+cVC7ro9kHra2X7TNm9bXvOmjYngVHXr2GKjwS GJmowTs68FycHSGzSzmujytt6/pnfMuVdlAqeWU8mFo+SllictQQYPegOGDe0OJ3 6F9oxuIWi1O1OiItXiDx0hgKgAifrvXtvhgcZiBXCK0aQfprxVA2Q4xgNsIR5ZnW cfhDLJzHUyaU6gHWdiwOrdcB2elFCZ3EEevkUSDpzp2XivKLH11gr3y9v959benU QxV5HI21GZSsTweAsRhjHDKgZ5U4XEJDkny4ZoM/wYdNeuxMsYXQvQCC/81854Wg == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 49EEF7E497; Wed, 13 Dec 2017 16:20:52 -0500 (EST) From: Thomas Monjalon To: Stephen Hemminger Cc: Ricardo Roldan , users@dpdk.org, dev@dpdk.org Date: Wed, 13 Dec 2017 22:20:51 +0100 Message-ID: <2478248.5ES5OfLd7E@xps> In-Reply-To: <20171213131009.18a4f821@xeon-e3> References: <1581834.O1SaQGJnzN@xps> <20171213131009.18a4f821@xeon-e3> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [dpdk-users] attach/detach on secondary process 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, 13 Dec 2017 21:20:53 -0000 13/12/2017 22:10, Stephen Hemminger: > On Wed, 13 Dec 2017 22:00:48 +0100 > Thomas Monjalon wrote: > > > 13/12/2017 18:09, Stephen Hemminger: > > > Many DPDK drivers require that setup and initialization be done by > > > the primary process. This is mostly to avoid dealing with concurrency since > > > there can be multiple secondary processes. > > > > I think we should consider this limitation as a bug. > > We must allow a secondary process to initialize a device. > > The race in device creation must be fixed. > > > > Secondary processes should be able to do setup. > But it is up to the application not to do it concurrently from multiple > processes. Yes there can be synchronization between processes. But I think it is safer to fix the device creation race in ethdev. Note that I am not talking about configuration concurrency, but just race in probing.