The port ownership concept was introduced in ethdev in DPDK 18.02.
Not sure it is used by applications except those using failsafe or netvsc.
It can also be used by libraries or applications to sort out
how ports are controlled.
Hiding sub-ports controlled by failsafe or netvsc look to be enough
j
On 10/28/2021 9:55 AM, Andrew Rybchenko wrote:
On 10/28/21 11:37 AM, Kinsella, Ray wrote:
On 28/10/2021 09:34, Thomas Monjalon wrote:
The port ownership concept was introduced in ethdev in DPDK 18.02.
Not sure it is used by applications except those using failsafe or
netvsc.
It can also be
On 28/10/2021 09:34, Thomas Monjalon wrote:
The port ownership concept was introduced in ethdev in DPDK 18.02.
Not sure it is used by applications except those using failsafe or netvsc.
It can also be used by libraries or applications to sort out
how ports are controlled.
Hiding sub-ports con
On 10/28/21 11:37 AM, Kinsella, Ray wrote:
On 28/10/2021 09:34, Thomas Monjalon wrote:
The port ownership concept was introduced in ethdev in DPDK 18.02.
Not sure it is used by applications except those using failsafe or
netvsc.
It can also be used by libraries or applications to sort out
ho
On 10/28/2021 9:34 AM, Thomas Monjalon wrote:
The port ownership concept was introduced in ethdev in DPDK 18.02.
Not sure it is used by applications except those using failsafe or netvsc.
It can also be used by libraries or applications to sort out
how ports are controlled.
Hiding sub-ports cont
28/10/2021 12:22, Ferruh Yigit:
> On 10/28/2021 9:34 AM, Thomas Monjalon wrote:
> > The port ownership concept was introduced in ethdev in DPDK 18.02.
> > Not sure it is used by applications except those using failsafe or netvsc.
> > It can also be used by libraries or applications to sort out
> >
6 matches
Mail list logo