From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com
 [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 72636107A;
 Wed, 13 Dec 2017 22:00:50 +0100 (CET)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id D81A92094B;
 Wed, 13 Dec 2017 16:00:49 -0500 (EST)
Received: from frontend1 ([10.202.2.160])
 by compute1.internal (MEProxy); Wed, 13 Dec 2017 16:00:49 -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=4oqYr5giRQ7mMPn7riAx56oLY7
 +JiJJvBGlF8sYtXtY=; b=cjmaa2kg9mxCcqi1e6VVzgqVfOw8LSh5LvD532KtKy
 2yr0zj5uUPiCXmAXd8hhEBw4b6YFWYH5eq2M6z4QBy7+vs69nK/inXw0c4zABA74
 0zPd3vNRa5+ubG2yL5FPgsUUIM09hVnLDI5XmSlSgx7ge8CxcJCbTkCzl4ebOyJa
 E=
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=4oqYr5
 giRQ7mMPn7riAx56oLY7+JiJJvBGlF8sYtXtY=; b=cjknMVa4M5FG660XcSkyas
 qQ3FJDHt975uxg64AhrHHCcvhp3oPR/T2uk3o030sCQsMUprlEMhiqpLIrevmyOY
 51dPbu2oxwAQqUf6khH62uVrdB1haLU4et/rSCZSqAuUIqkD2803E6cmfmalOq8Q
 +rFGbPnhsgGLnVe2W1bVZTOBrrtEIOAHsi0JJG46ZoT4ahsob7C1doT0cgsBJ7Bz
 11YAVZ2LjV243p60j8oOet8olnBg2h/1YJVzCgHjaWTBLBbuahN5CDsK8SIMzOdB
 Ajku9zMoeMk4in8FLDgyF3z2ijijbJUE0MS3sUV1aixXmj8piLy/lj+xxoiOGczg
 ==
X-ME-Sender: <xms:AZUxWiqSQDyLFsZa8ck8QpgB5uizMCWG0URmo5Qa63LwSODrxvIb5w>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id 8117D7E3D5;
 Wed, 13 Dec 2017 16:00:49 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: Ricardo Roldan <rroldan@bequant.com>
Cc: users@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>,
 dev@dpdk.org
Date: Wed, 13 Dec 2017 22:00:48 +0100
Message-ID: <1581834.O1SaQGJnzN@xps>
In-Reply-To: <20171213090952.495bfb1b@xeon-e3>
References: <fb117eef-ddad-67f6-8e0f-6febdbc0aeed@bequant.com>
 <7a3a2174-831f-caa8-ed33-0f06133c96a2@bequant.com>
 <20171213090952.495bfb1b@xeon-e3>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-users] attach/detach on secondary process
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Dec 2017 21:00:50 -0000

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.