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 20:32:47 +0000
Message-ID: <d3102b55df4f4ebf9a731f87378798b2@napatech.com>
References: <1512027330-30030-1-git-send-email-yliu@fridaylinux.org>
 <2746853.LkVxvJSmNi@xps> <dd55db8afed749f5a71f919e7f5d7633@napatech.com>
 <40957417.C216t4nj8c@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 mail01.napatech.com (mail01.napatech.com [188.120.77.121])
 by dpdk.org (Postfix) with ESMTP id AC68A8E01
 for <dev@dpdk.org>; Fri,  5 Jan 2018 21:32:48 +0100 (CET)
In-Reply-To: <40957417.C216t4nj8c@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 16:34
>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 15:14, Finn Christensen:
>> From: Thomas Monjalon [mailto:thomas@monjalon.net]
>> >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 Lin=
ux.
>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 mechanism to enable individual ports at startup also. We will
>> continue to use proprietary devargs passed by whiterlist to the PMD prob=
e
>function.
>> What we needed was a way to select the individual ports, by using
>> rte_eth_dev_get_port_by_name().
>
>The whitelist will be replaced by this new syntax.
>And yes, you can have your own driver-specific property with this syntax.

That's fine.

>
>> >> We will not be able to support the dev_port property, that will not
>> >> work for
>> >us.
>> >> At least not for now.
>
>It leads to a totally different question:
>Can we discuss again how to integrate your driver in DPDK upstream?
>Please explain again your situation in a new thread.

Sure, I'll get back to you in a new thread. Thanks!