From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f66.google.com (mail-pg0-f66.google.com [74.125.83.66]) by dpdk.org (Postfix) with ESMTP id 387131D90 for ; Wed, 13 Dec 2017 22:10:13 +0100 (CET) Received: by mail-pg0-f66.google.com with SMTP id b11so1881238pgu.13 for ; Wed, 13 Dec 2017 13:10:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=K4pa58kUvgzMzp1xe46HIczDUCRDWR17RGV2Mw3ccf4=; b=t2zU/oIw6861+PKjYomKXRe6oqGHKo7TixVIFUosTrIyhnfy8FLGJ9syW6YXJM2m6g NXCct1ehV5x5cL9GmyvtFgKxNBso0MjB3/Zx3CseruCtrRRN7RIuiGS7zr/wpSj5r3tl KaykqYLfIo7OPS1+fCw9YAyeyg/e6VhS1T+tsREaGeaO/GhWm/95Rp/xWRigU21Yr2NX UCiwgNPu0dZTl+4pseTQ189dHxOD7qWWNefW2f6sKKS5GWrt2/ExIYDwNsXp4VFnIs4G 0zPz7Du2eYYtYu4Fb/pNIXNyd2wb1yoYp3mOy0q5QRdltuCiTDcuM3uX/4av43F+jqEI 6Hgw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=K4pa58kUvgzMzp1xe46HIczDUCRDWR17RGV2Mw3ccf4=; b=uEXDhLAG6PcZHKacty7nr0q5GPzJxTpbuReCAp3gfG8P8i/Yp28P23DOLHqJPFTh9/ PO5Q/PIpIhXsKe7qn8Gg/WT5zMkI+nDUxv5Xg9jxGCj0HyOAbXK/RwL3Z9edmfGn3mE5 Eg1Lfuk4DQHWN2G8byJIqyd+AUJqR97QYdxi/TPSGrxmI/DGH3KUZGnnsI87CARxCdQ4 KInKxeWhgEfn6F+3d3FydP4O50YOfaiHceyHlKxsunlERDrfGqVT9IhTrDFnZWxQbN3Y Me642Tem1yLQ2TW1n6jAuFdB0qcDBglOqgVou5aDQI4lO+ejusY63AyHzpurjOp60lUG RTRQ== X-Gm-Message-State: AKGB3mLg69JtIqvRr0cUX2VsmzR2wGB7QpfvRoeK7GO2viAvQG7REbvz tvzB380U4Su4Btg/qVN0RDSxLQ== X-Google-Smtp-Source: ACJfBov+2/cxBd5RDhJvX/NjgMO5fuPgKI5m1L9PXcbBfcbkq99VLptL71ddy/wacA/pZvTq8Ld40g== X-Received: by 10.84.143.34 with SMTP id 31mr7263262ply.446.1513199412287; Wed, 13 Dec 2017 13:10:12 -0800 (PST) Received: from xeon-e3 (76-14-207-240.or.wavecable.com. [76.14.207.240]) by smtp.gmail.com with ESMTPSA id y1sm4403476pgq.41.2017.12.13.13.10.11 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 13 Dec 2017 13:10:12 -0800 (PST) Date: Wed, 13 Dec 2017 13:10:09 -0800 From: Stephen Hemminger To: Thomas Monjalon Cc: Ricardo Roldan , users@dpdk.org, dev@dpdk.org Message-ID: <20171213131009.18a4f821@xeon-e3> In-Reply-To: <1581834.O1SaQGJnzN@xps> 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 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Dec 2017 21:10:13 -0000 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.