Re: [dpdk-dev] [PATCH 3/5] ethdev: allow iterating with only class filter

2018-10-08 Thread Andrew Rybchenko
On 10/8/18 11:07 AM, Thomas Monjalon wrote: 08/10/2018 09:20, Andrew Rybchenko: On 10/8/18 1:25 AM, Thomas Monjalon wrote: If no rte_device is given in the iterator, eth_dev_match() is looking at all ports without any restriction, except the ethdev kvargs filter. It allows to iterate with a de

Re: [dpdk-dev] [PATCH 3/5] ethdev: allow iterating with only class filter

2018-10-08 Thread Thomas Monjalon
08/10/2018 09:20, Andrew Rybchenko: > On 10/8/18 1:25 AM, Thomas Monjalon wrote: > > If no rte_device is given in the iterator, > > eth_dev_match() is looking at all ports without any restriction, > > except the ethdev kvargs filter. > > > > It allows to iterate with a devargs filter referencing on

Re: [dpdk-dev] [PATCH 3/5] ethdev: allow iterating with only class filter

2018-10-08 Thread Andrew Rybchenko
On 10/8/18 1:25 AM, Thomas Monjalon wrote: If no rte_device is given in the iterator, eth_dev_match() is looking at all ports without any restriction, except the ethdev kvargs filter. It allows to iterate with a devargs filter referencing only some ethdev parameters. The format (from the new dev

[dpdk-dev] [PATCH 3/5] ethdev: allow iterating with only class filter

2018-10-07 Thread Thomas Monjalon
If no rte_device is given in the iterator, eth_dev_match() is looking at all ports without any restriction, except the ethdev kvargs filter. It allows to iterate with a devargs filter referencing only some ethdev parameters. The format (from the new devargs syntax) is: class=eth,paramY=Y