21/09/2018 14:16, Gaëtan Rivet:
> On Thu, Sep 20, 2018 at 06:17:13PM +0200, Thomas Monjalon wrote:
> > 19/09/2018 18:03, Gaetan Rivet:
> > > The eth device class can now parse a field name,
> > > matching the eth_dev name with one passed as
> > >
> > >"class=eth,name=xx"
> >
> > I am not
On Thu, Sep 20, 2018 at 06:17:13PM +0200, Thomas Monjalon wrote:
> 19/09/2018 18:03, Gaetan Rivet:
> > The eth device class can now parse a field name,
> > matching the eth_dev name with one passed as
> >
> >"class=eth,name=xx"
>
> I am not sure what is the purpose of the "name" property.
19/09/2018 18:03, Gaetan Rivet:
> The eth device class can now parse a field name,
> matching the eth_dev name with one passed as
>
>"class=eth,name=xx"
I am not sure what is the purpose of the "name" property.
I think we should not need it to choose a port by its ethdev name.
If you are
The eth device class can now parse a field name,
matching the eth_dev name with one passed as
"class=eth,name=xx"
Signed-off-by: Gaetan Rivet
Acked-by: Andrew Rybchenko
---
lib/librte_ethdev/rte_class_eth.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/lib/librte_ethdev/rte
4 matches
Mail list logo