From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com
 [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 4539B1B322
 for <dev@dpdk.org>; Fri, 19 Jan 2018 15:14:23 +0100 (CET)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id 9A53120B52;
 Fri, 19 Jan 2018 09:14:22 -0500 (EST)
Received: from frontend1 ([10.202.2.160])
 by compute1.internal (MEProxy); Fri, 19 Jan 2018 09:14:22 -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=EfFKBhWjYfKLTaUSZPRdyTiMHr
 OlcusjFpOtc/6GDak=; b=oZHSKgBs0Ixy16RM686w8rzPLdxirOKPYpapmQFXUp
 7E7OAHYa4AHHk0uyjN1oJ52W43QzxKtIW0/zk3DpSRGV4V88P9HTLVmZ8OU2Cvsx
 UJz34lpj8V7/qNdp2YIz4nWQrCDGDsoo+WZjssyt/dkuB70moGFRCm8E7cfBGTse
 o=
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=EfFKBh
 WjYfKLTaUSZPRdyTiMHrOlcusjFpOtc/6GDak=; b=Kf3+91VcOIzh2zHJ7PqTrz
 oyBfuJCaCP4PgF9D/gf1Li3aXRxB6qSrmxzOAnFsPZG9z+52FTrv1u3T799TJtsq
 M0WUL5mdbBitDOY2xYFKWvq1Iful+JRTyk8p8y0rVoV4mqL7Z9IFQ1zfuNk1TiWy
 L56ucez+AeMrtBnUpXclmNwpVJC06PR/yMlvFvr+Vc1y6xrGe6HeQoPMPKxMizqD
 X3Y4Judy7nSnKIQ1cvZWQNh3VLxV0eXALaFaBNXmMC3IJJOANmNfJcYq8E/bblfE
 5XQRDWWEGa9QgjEEghIDi1Kb0KAlXmAw8Pu4Utv/XV2QkR8W/I6Xpv/Ik1bNjyAQ
 ==
X-ME-Sender: <xms:Pv1hWv6fL7s6Tj7YvckU71pEYK-MiQjmgposZDjdlgWPuo5tnodVVQ>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id 3DF9D7E0FA;
 Fri, 19 Jan 2018 09:14:22 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: dev@dpdk.org, Matan Azrad <matan@mellanox.com>,
 Bruce Richardson <bruce.richardson@intel.com>, "Ananyev,
 Konstantin" <konstantin.ananyev@intel.com>,
 Gaetan Rivet <gaetan.rivet@6wind.com>, "Wu, Jingjing" <jingjing.wu@intel.com>
Date: Fri, 19 Jan 2018 15:13:47 +0100
Message-ID: <1526278.zylApLv2LJ@xps>
In-Reply-To: <20180119133019.GB5342@hmswarspite.think-freely.org>
References: <20180118131017.GA1622@hmswarspite.think-freely.org>
 <AM6PR0502MB37970C027884268F8690AC51D2EF0@AM6PR0502MB3797.eurprd05.prod.outlook.com>
 <20180119133019.GB5342@hmswarspite.think-freely.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] [PATCH v2 2/6] ethdev: add port ownership
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://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: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jan 2018 14:14:23 -0000

19/01/2018 14:30, Neil Horman:
> So it seems like the real point of contention that we need to settle here is,
> what codifies an 'owner'.  Must it be a specific execution context, or can we
> define any arbitrary section of code as being an owner?  I would agrue against
> the latter.

This is the first thing explained in the cover letter:
"2. The port usage synchronization will be managed by the port owner."
There is no intent to manage the threads synchronization for a given port.
It is the responsibility of the owner (a code object) to configure its
port via only one thread.
It is consistent with not trying to manage threads synchronization
for Rx/Tx on a given queue.