13/12/2017 22:10, Stephen Hemminger:
> On Wed, 13 Dec 2017 22:00:48 +0100
> Thomas Monjalon wrote:
>
> > 13/12/2017 18:09, Stephen Hemminger:
> > > Many DPDK drivers require that setup and initialization be done by
> > > the primary process. This is mostly to avoid dealing
On Wed, 13 Dec 2017 22:00:48 +0100
Thomas Monjalon wrote:
> 13/12/2017 18:09, Stephen Hemminger:
> > Many DPDK drivers require that setup and initialization be done by
> > the primary process. This is mostly to avoid dealing with concurrency since
> > there can be multiple
13/12/2017 18:09, Stephen Hemminger:
> Many DPDK drivers require that setup and initialization be done by
> the primary process. This is mostly to avoid dealing with concurrency since
> there can be multiple secondary processes.
I think we should consider this limitation as a bug.
We must allow a
On Wed, 13 Dec 2017 17:58:53 +0100
Ricardo Roldan wrote:
> Hi,
>
> We have a multi-process application and we need to support
> attaching/detaching of ports. We are using the 17.11 version with the
> Intel x520 (ixgbe driver) and virtio.
>
> At the time we initialize our
Hi,
We have a multi-process application and we need to support
attaching/detaching of ports. We are using the 17.11 version with the
Intel x520 (ixgbe driver) and virtio.
At the time we initialize our processes there are not any devices binded
with the DPDK drivers, so we initialize all