From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id E7E801B206 for ; Wed, 11 Oct 2017 23:56:56 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 653D6212F0; Wed, 11 Oct 2017 17:56:55 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 11 Oct 2017 17:56:56 -0400 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=mQJly0+RdONkk7uaDnpNQcgXk8 6qBwvMg3perGK82cE=; b=BQl+mmiIlnwv3MyCUXWHMj4aM1KOIIhnSsLCY8eU61 eNMZ81WFDrOuA+LNjttQdTUtGOB3DgGlLWS2mscrvqp+KDLFi6CIwsnnn0Y770Iw bg9La+jtQPgGoXj5H5/CvC3+e+hDWk0fCDe2eq4AiT4XCFDx/siEK4LurgBbhiGA k= 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=mQJly0 +RdONkk7uaDnpNQcgXk86qBwvMg3perGK82cE=; b=qFUGQgzBG/7Zjn3IVbTRC2 qvTnQjwiVM/5DQ+DA3L6Y+ZVT6xAQSXOShDqPohlaVuKXl/2j3OmnlcXPh0rIqLl M0DzTzxsCfYMdafjBeFzwazTCkPIryOji29rC/HHns5ZmXT0ra71GwcPimB2X4pA 9b/ngBZHXj13sUI5Nfoa09rnFgGK3hylAGrgnomm+Ixb3PxNtFrJ9TwoJgf7f+rH BlN1d9soASJzy/gUUGXbLxhXorupLF9iTcBOsZHEoNuRmGIg8zz1SiyS80Qc2+ws XA3p3AsdcK1bFUZeun1JLPhtWM75VkQmxqZ0eBE4cTH+USWPPI0OXRm7RqeCLkBw == 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 6D5A37EAFA; Wed, 11 Oct 2017 17:56:55 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit , ciara.loftus@intel.com Cc: dev@dpdk.org, Adrien Mazarguil , ktraynor@redhat.com, gaetan.rivet@6wind.com, jblunck@infradead.org Date: Wed, 11 Oct 2017 23:56:54 +0200 Message-ID: <5659846.3hnuzHVyBs@xps> In-Reply-To: <20170922145722.GA3871@6wind.com> References: <20170922113007.43385-1-ferruh.yigit@intel.com> <20170922145722.GA3871@6wind.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] ethdev: revert use device name from device structure 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, 11 Oct 2017 21:56:57 -0000 22/09/2017 16:57, Adrien Mazarguil: > On Fri, Sep 22, 2017 at 12:30:07PM +0100, Ferruh Yigit wrote: > > This reverts commit a1e7c17555e8f77d520ba5f06ed26c00e77a2bd1. > > > > Original commit assumes there is 1:1 mapping between physical device and > > ethdev port, so that device name can be used per port instead of ethdev > > name field. > > > > But one physical device may have multiple ethdev ports and each port > > needs its own unique name. > > > > One issue reported here: > > http://dpdk.org/ml/archives/users/2017-September/002484.html > > > > So reverting back the commit to continue using ethdev name field per > > port. > > > > Reported-by: Adrien Mazarguil > > Signed-off-by: Ferruh Yigit > > Acked-by: Adrien Mazarguil Acked-by: Thomas Monjalon I agree we must keep separate the device name and the ethdev port name. About the OVS issue (Cc'ing people), it would be valuable to work in DPDK to establish a reliable syntax to describe a device or a port. This is what we call devargs ; it is still a work in progress.