Re: [dpdk-dev] standardize device identification

2018-01-05 Thread Finn Christensen
>Subject: Re: [dpdk-dev] standardize device identification > >05/01/2018 15:14, Finn Christensen: >> From: Thomas Monjalon [mailto:tho...@monjalon.net] >> >05/01/2018 12:09, Finn Christensen: >> >> From: Thomas Monjalon >> >> Which property can help t

Re: [dpdk-dev] standardize device identification

2018-01-05 Thread Thomas Monjalon
05/01/2018 15:14, Finn Christensen: > From: Thomas Monjalon [mailto:tho...@monjalon.net] > >05/01/2018 12:09, Finn Christensen: > >> From: Thomas Monjalon > >> Which property can help to distinguish Napatech ports? > >> Can you use class=eth,dev_port=X ? > >> The dev_port property will

Re: [dpdk-dev] standardize device identification

2018-01-05 Thread Finn Christensen
>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=eth,dev_port=X ? >> The dev_port property will use /sys

Re: [dpdk-dev] standardize device identification

2018-01-05 Thread Thomas Monjalon
05/01/2018 12:09, Finn Christensen: > From: Thomas Monjalon > 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 o

Re: [dpdk-dev] standardize device identification

2018-01-05 Thread Finn Christensen
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_

Re: [dpdk-dev] standardize device identification

2018-01-05 Thread Thomas Monjalon
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

Re: [dpdk-dev] standardize device identification

2018-01-04 Thread Finn Christensen
Subject: Re: [dpdk-dev] standardize device identification Changing the title and adding more comments inline: 19/12/2017 00:05, Thomas Monjalon: > Let's summarize and resume this thread. > > We need a generic syntax to describe a device. > T

Re: [dpdk-dev] standardize device identification

2017-12-22 Thread Thomas Monjalon
22/12/2017 08:01, Shreyansh Jain: > On Thursday 21 December 2017 03:32 AM, Thomas Monjalon wrote: > > Changing the title and adding more comments inline: > > > > 19/12/2017 00:05, Thomas Monjalon: > >> Let's summarize and resume this thread. > >> > >> We need a generic syntax to describe a device.

Re: [dpdk-dev] standardize device identification

2017-12-21 Thread Shreyansh Jain
On Thursday 21 December 2017 03:32 AM, Thomas Monjalon wrote: Changing the title and adding more comments inline: 19/12/2017 00:05, Thomas Monjalon: Let's summarize and resume this thread. We need a generic syntax to describe a device. This syntax can be used - before initializing the

Re: [dpdk-dev] standardize device identification

2017-12-20 Thread Thomas Monjalon
Changing the title and adding more comments inline: 19/12/2017 00:05, Thomas Monjalon: > Let's summarize and resume this thread. > > We need a generic syntax to describe a device. > This syntax can be used > - before initializing the device (i.e. whitelist/blacklist) > - or after the