From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Ricardo Roldan <rroldan@bequant.com>, users@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-users] attach/detach on secondary process
Date: Wed, 13 Dec 2017 22:20:51 +0100 [thread overview]
Message-ID: <2478248.5ES5OfLd7E@xps> (raw)
In-Reply-To: <20171213131009.18a4f821@xeon-e3>
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.
prev parent reply other threads:[~2017-12-13 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[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-users] attach/detach on secondary process Thomas Monjalon
2017-12-13 21:10 ` Stephen Hemminger
2017-12-13 21:20 ` Thomas Monjalon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2478248.5ES5OfLd7E@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=rroldan@bequant.com \
--cc=stephen@networkplumber.org \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.