From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-users] attach/detach on secondary process
Date: Wed, 13 Dec 2017 22:00:48 +0100
Message-ID: <1581834.O1SaQGJnzN@xps>
References: <fb117eef-ddad-67f6-8e0f-6febdbc0aeed@bequant.com>
 <7a3a2174-831f-caa8-ed33-0f06133c96a2@bequant.com>
 <20171213090952.495bfb1b@xeon-e3>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: users@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>,
 dev@dpdk.org
To: Ricardo Roldan <rroldan@bequant.com>
Return-path: <dev-bounces@dpdk.org>
In-Reply-To: <20171213090952.495bfb1b@xeon-e3>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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.