From mboxrd@z Thu Jan  1 00:00:00 1970
From: Finn Christensen <fc@napatech.com>
Subject: Re: standardize device identification
Date: Fri, 5 Jan 2018 14:14:29 +0000
Message-ID: <dd55db8afed749f5a71f919e7f5d7633@napatech.com>
References: <1512027330-30030-1-git-send-email-yliu@fridaylinux.org>
 <3183370.0ufOrFygau@xps> <c4e698540a754f6a830621ef0a859712@napatech.com>
 <2746853.LkVxvJSmNi@xps>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: "dev@dpdk.org" <dev@dpdk.org>, Yuanhan Liu <yliu@fridaylinux.org>, "Adrien
 Mazarguil" <adrien.mazarguil@6wind.com>, Ciara Loftus
 <ciara.loftus@intel.com>, Kevin Traynor <ktraynor@redhat.com>,
 "stephen@networkplumber.org" <stephen@networkplumber.org>,
 "ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Return-path: <dev-bounces@dpdk.org>
Received: from mail02.napatech.com (mail02.napatech.com [188.120.77.119])
 by dpdk.org (Postfix) with ESMTP id E404C1B16F
 for <dev@dpdk.org>; Fri,  5 Jan 2018 15:14:30 +0100 (CET)
In-Reply-To: <2746853.LkVxvJSmNi@xps>
Content-Language: en-US
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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>


>-----Original Message-----
>From: Thomas Monjalon [mailto:thomas@monjalon.net]
>Sent: 5. januar 2018 13:02
>To: Finn Christensen <fc@napatech.com>
>Cc: dev@dpdk.org; Yuanhan Liu <yliu@fridaylinux.org>; Adrien Mazarguil
><adrien.mazarguil@6wind.com>; Ciara Loftus <ciara.loftus@intel.com>; Kevin
>Traynor <ktraynor@redhat.com>; stephen@networkplumber.org;
>ferruh.yigit@intel.com
>Subject: Re: [dpdk-dev] standardize device identification
>
>05/01/2018 12:09, Finn Christensen:
>> From: Thomas Monjalon
>>     Which property can help to distinguish Napatech ports?
>>     Can you use class=3Deth,dev_port=3DX ?
>>     The dev_port property will use /sys/class/net/DEV/dev_port on Linux.=
 Is it
>>     OK for you?
>>
>> Actually, what we were thinking of was using the mac property in the
>> class category to distinguish our ports.
>> For instance:
>> -w bus=3Dpci,id=3D0000:01:00.0/class=3Deth,mac=3D00:11:22:33:44:55
>> or simply:
>> -w class=3Deth,mac=3D00:11:22:33:44:55
>
>The problem with the mac property is that it cannot be used for
>white/blacklisting in DPDK because the MAC is not known before port
>initialization.
>

Sure, that makes sense. I just for a minute thought that we could use that=
=20
mechanism to enable individual ports at startup also. We will continue to=20
use proprietary devargs passed by whiterlist to the PMD probe function.
What we needed was a way to select the individual ports, by using=20
rte_eth_dev_get_port_by_name().=20


>> We will not be able to support the dev_port property, that will not work=
 for
>us.
>> At least not for now.