* Re: [dpdk-dev] [dpdk-users] attach/detach on secondary process
[not found] ` <20171213090952.495bfb1b@xeon-e3>
@ 2017-12-13 21:00 ` Thomas Monjalon
2017-12-13 21:10 ` Stephen Hemminger
0 siblings, 1 reply; 3+ messages in thread
From: Thomas Monjalon @ 2017-12-13 21:00 UTC (permalink / raw)
To: Ricardo Roldan; +Cc: users, Stephen Hemminger, dev
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 secondary process to initialize a device.
The race in device creation must be fixed.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] [dpdk-users] attach/detach on secondary process
2017-12-13 21:00 ` [dpdk-dev] [dpdk-users] attach/detach on secondary process Thomas Monjalon
@ 2017-12-13 21:10 ` Stephen Hemminger
2017-12-13 21:20 ` Thomas Monjalon
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Hemminger @ 2017-12-13 21:10 UTC (permalink / raw)
To: Thomas Monjalon; +Cc: Ricardo Roldan, users, dev
On Wed, 13 Dec 2017 22:00:48 +0100
Thomas Monjalon <thomas@monjalon.net> 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 secondary processes.
>
> I think we should consider this limitation as a bug.
> We must allow a secondary process to initialize a device.
> The race in device creation must be fixed.
>
Secondary processes should be able to do setup.
But it is up to the application not to do it concurrently from multiple
processes.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] [dpdk-users] attach/detach on secondary process
2017-12-13 21:10 ` Stephen Hemminger
@ 2017-12-13 21:20 ` Thomas Monjalon
0 siblings, 0 replies; 3+ messages in thread
From: Thomas Monjalon @ 2017-12-13 21:20 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: Ricardo Roldan, users, dev
13/12/2017 22:10, Stephen Hemminger:
> On Wed, 13 Dec 2017 22:00:48 +0100
> Thomas Monjalon <thomas@monjalon.net> 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 secondary processes.
> >
> > I think we should consider this limitation as a bug.
> > We must allow a secondary process to initialize a device.
> > The race in device creation must be fixed.
> >
>
> Secondary processes should be able to do setup.
> But it is up to the application not to do it concurrently from multiple
> processes.
Yes there can be synchronization between processes.
But I think it is safer to fix the device creation race in ethdev.
Note that I am not talking about configuration concurrency,
but just race in probing.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-12-13 21:20 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <fb117eef-ddad-67f6-8e0f-6febdbc0aeed@bequant.com>
[not found] ` <7a3a2174-831f-caa8-ed33-0f06133c96a2@bequant.com>
[not found] ` <20171213090952.495bfb1b@xeon-e3>
2017-12-13 21:00 ` [dpdk-dev] [dpdk-users] attach/detach on secondary process Thomas Monjalon
2017-12-13 21:10 ` Stephen Hemminger
2017-12-13 21:20 ` Thomas Monjalon
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).