From: Finn Christensen <fc@napatech.com>
To: Thomas Monjalon <thomas@monjalon.net>
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>
Subject: Re: [dpdk-dev] standardize device identification
Date: Fri, 5 Jan 2018 11:09:31 +0000 [thread overview]
Message-ID: <c4e698540a754f6a830621ef0a859712@napatech.com> (raw)
In-Reply-To: <3183370.0ufOrFygau@xps>
-----Original Message-----
From: Thomas Monjalon [mailto:thomas@monjalon.net]
Sent: 5. januar 2018 09:40
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 08:52, Finn Christensen:
> From: Thomas
> > It may look like this:
> >
> >
bus=BUS_NAME,id=BUS_ID/class=CLASS_NAME,dev_port=PORT_NUM,
> >
mac=MAC_ADDRESS/driver=DRIVER_NAME,driverspecificproperty=VALUE
[...]
> We also need to distinguish between multiple ports sitting on same PCI
bus ID.
> and from our point of view, this will fully cover our needs.
Which property can help to distinguish Napatech ports?
Can you use class=eth,dev_port=X ?
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=pci,id=0000:01:00.0/class=eth,mac=00:11:22:33:44:55
or simply:
-w class=eth,mac=00:11:22:33:44:55
We will not be able to support the dev_port property, that will not work for us.
At least not for now.
Regards,
Finn
next prev parent reply other threads:[~2018-01-05 11:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 7:35 [dpdk-dev] [PATCH] [RFC] ether: standardize getting the port by name Yuanhan Liu
2017-11-30 17:15 ` Stephen Hemminger
2017-11-30 17:35 ` Thomas Monjalon
2017-11-30 21:21 ` Stephen Hemminger
2017-11-30 21:44 ` Thomas Monjalon
2017-12-01 9:47 ` Gaëtan Rivet
2017-12-04 13:55 ` Yuanhan Liu
2017-12-05 11:04 ` Adrien Mazarguil
2017-12-05 13:20 ` Thomas Monjalon
2017-12-05 13:58 ` Yuanhan Liu
2017-12-05 15:28 ` Thomas Monjalon
2017-12-05 17:22 ` Adrien Mazarguil
2017-12-06 15:49 ` Yuanhan Liu
2017-12-18 22:25 ` Thomas Monjalon
2017-12-18 22:30 ` Stephen Hemminger
2017-12-18 22:41 ` Thomas Monjalon
2017-12-18 23:05 ` Thomas Monjalon
2017-12-20 22:02 ` [dpdk-dev] standardize device identification Thomas Monjalon
2017-12-22 7:01 ` Shreyansh Jain
2017-12-22 9:00 ` Thomas Monjalon
2018-01-05 7:52 ` Finn Christensen
2018-01-05 8:39 ` Thomas Monjalon
2018-01-05 11:09 ` Finn Christensen [this message]
2018-01-05 12:01 ` Thomas Monjalon
2018-01-05 14:14 ` Finn Christensen
2018-01-05 15:34 ` Thomas Monjalon
2018-01-05 20:32 ` Finn Christensen
2018-01-16 20:20 ` [dpdk-dev] [PATCH] [RFC] ether: standardize getting the port by name Ferruh Yigit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c4e698540a754f6a830621ef0a859712@napatech.com \
--to=fc@napatech.com \
--cc=adrien.mazarguil@6wind.com \
--cc=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ktraynor@redhat.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=yliu@fridaylinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).