From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [dpdk-users] attach/detach on secondary process Date: Wed, 13 Dec 2017 13:10:09 -0800 Message-ID: <20171213131009.18a4f821@xeon-e3> References: <7a3a2174-831f-caa8-ed33-0f06133c96a2@bequant.com> <20171213090952.495bfb1b@xeon-e3> <1581834.O1SaQGJnzN@xps> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Ricardo Roldan , users@dpdk.org, dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mail-pg0-f65.google.com (mail-pg0-f65.google.com [74.125.83.65]) by dpdk.org (Postfix) with ESMTP id 51E892030 for ; Wed, 13 Dec 2017 22:10:13 +0100 (CET) Received: by mail-pg0-f65.google.com with SMTP id y6so1896770pgp.4 for ; Wed, 13 Dec 2017 13:10:13 -0800 (PST) In-Reply-To: <1581834.O1SaQGJnzN@xps> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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.