From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 7B473A49A for ; Wed, 24 Jan 2018 09:10:48 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E46532258D; Wed, 24 Jan 2018 03:10:47 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 24 Jan 2018 03:10:47 -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=YN+uNub9oRrsxLqOWY8yaz6Owz +nq24ilSE2Zkw8fAk=; b=cyfvJ6UhmA0efTBezTKCRItEwDlYNdAn1/QPB37qAb d15KSXkVdd3vWpljrTFTy12jg4rqRnyIHn7s0kbKuiJSq1f4iRj5SMZMDFvOVfbN ctv8umSfVNMS5fkbY4L2j84MLY+AWZ1V099014qlIs7sL0TCn2b/KTtVJd1W8Bv0 Q= 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=YN+uNu b9oRrsxLqOWY8yaz6Owz+nq24ilSE2Zkw8fAk=; b=H9vu+nFtGqzJNDq2PNryPl zylmlILWr01jlFfX+r0PeaHLzx2Lck0+lo77VkXM+RasCHrQlBy1xpX5AtHQIkec ii8E0b06H6GZ7M2nZyF7L8lStraNmo6If7/V9kZbtcBPGaP1CE92F82qWWQ4nuRg LzCm83B3nbp6nS+2CuzAQqpF0MegZQte9wuQRDXSY5VtDTA34ktPGRPaNXw+lvhs SKCvCIBdL4KdSGpjffQrPmEU8e5PiSRU2w6bIxgPh+V4dFBf1M4O08Fa6ubkavKJ /do50ZbB/S/pb+21brTbYv7oQOHbSEoWfbw38FprA0Fj2bxTb0BbsTqpBn7RcMqg == 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 8CE7A7E125; Wed, 24 Jan 2018 03:10:47 -0500 (EST) From: Thomas Monjalon To: "Ananyev, Konstantin" Cc: Matan Azrad , =?ISO-8859-1?Q?Ga=EBtan?= Rivet , "Wu, Jingjing" , dev@dpdk.org, Neil Horman , "Richardson, Bruce" Date: Wed, 24 Jan 2018 09:10:03 +0100 Message-ID: <1682675.gfxK9aSxec@xps> In-Reply-To: <2601191342CEEE43887BDE71AB9772588628298E@irsmsx105.ger.corp.intel.com> References: <1515318351-4756-1-git-send-email-matan@mellanox.com> <3663694.426ICJToDY@xps> <2601191342CEEE43887BDE71AB9772588628298E@irsmsx105.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3 7/7] app/testpmd: adjust ethdev port ownership 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, 24 Jan 2018 08:10:48 -0000 23/01/2018 22:18, Ananyev, Konstantin: > > > > 23/01/2018 16:18, Ananyev, Konstantin: > > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ananyev, Konstantin > > > > From: Thomas Monjalon [mailto:thomas@monjalon.net] > > > > > 23/01/2018 14:34, Ananyev, Konstantin: > > > > > > If that' s the use case, then I think you need to set device ownership at creation time - > > > > > > inside dev_allocate(). > > > > > > Again that would avoid such racing conditions inside testpmd. > > > > > > > > > > The devices must be allocated at a low level layer. > > > > > > > > No one arguing about that. > > > > But we can provide owner id information to the low level. > > > > Sorry, you did not get it. > > Might be. > > > We cannot provide owner id at the low level > > because it is not yet decided who will be the owner > > before the port is allocated. > > Why is that? > What prevents us decide who will manage that device *before* allocating port of it? > IMO we do have all needed information at that stage. We don't have the information. It is a new device, it is matched by a driver which allocates a port. I don't see where the higher level can interact here. And even if you manage a trick, the higher level needs to read the port informations to decide the ownership. > > > > > When a new device appears (hotplug), an ethdev port should be allocated > > > > > automatically if it passes the whitelist/blacklist policy test. > > > > > Then we must decide who will manage this device. > > > > > I suggest notifying the DPDK libs first. > > > > > So a DPDK lib or PMD like failsafe can have the priority to take the > > > > > ownership in its notification callback. > > > > > > > > Possible, but seems a bit overcomplicated. > > > > Why not just: > > > > > > > > Have a global variable process_default_owner_id, that would be init once at startup. > > > > Have an LTS variable default_owner_id. > > > > It will be used by rte_eth_dev_allocate() caller can set dev->owner_id at creation time, > > > > so port allocation and setting ownership - will be an atomic operation. > > > > At the exit rte_eth_dev_allocate() will always reset default_owner_id=0: > > > > > > > > rte_eth_dev_allocate(...) > > > > { > > > > lock(owner_lock); > > > > > > > > owner = RTE_PER_LCORE(default_owner_id); > > > > if (owner == 0) > > > > owner = process_default_owner_id; > > > > set_owner(port, ..., owner); > > > > unlock(owner_lock); > > > > RTE_PER_LCORE(default_owner_id) = 0; > > > > > > Or probably better to leave default_owner_id reset to the caller. > > > Another thing - we can use same LTS variable in all control ops to > > > allow/disallow changing of port configuration based on ownership. > > > Konstantin > > > > > > > } > > > > > > > > So callers who don't need any special ownership - don't need to do anything. > > > > Special callers (like failsafe) can set default_owenr_id just before calling hotplug > > > > handling routine. > > > > No, hotplug will not be a routine. > > I am talking about real hotplug, like a device which appears in the VM. > > This new device must be handled by EAL and probed automatically if > > comply with whitelist/blacklist policy given by the application or user. > > Real hotplug is asynchronous. > > By 'asynchronous' here you mean it would be handled in the EAL interrupt thread > or something different? Yes, we receive an hotplug event which is processed in the event thread. > Anyway, I suppose you do need a function inside DPDK that will do the actual work in response > on hotplug event, right? Yes > That's what I refer to as 'hotplug routine' above. > > > We will just receive notifications that it appeared. > > > > Note: there is some temporary code in failsafe to manage some hotplug. > > This code must be removed when it will be properly handled in EAL. > > Ok, if it is just a temporary code, that would be removed soon - > then it definitely seems wrong to modify tespmd (or any other user app) > to comply with that temporary solution. It will be modified when EAL hotplug will be implemented. However, the ownership issue will be the same: we don't know the owner when allocating a port.