Re: [dpdk-users] attach/detach on secondary process

2017-12-13 Thread Thomas Monjalon
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

Re: [dpdk-users] attach/detach on secondary process

2017-12-13 Thread 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 with concurrency since > > there can be multiple

Re: [dpdk-users] attach/detach on secondary process

2017-12-13 Thread Thomas Monjalon
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

Re: [dpdk-users] attach/detach on secondary process

2017-12-13 Thread Stephen Hemminger
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

[dpdk-users] attach/detach on secondary process

2017-12-13 Thread Ricardo Roldan
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