From: Stephen Hemminger <stephen@networkplumber.org>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] Should we disallow running secondaries after primary has died?
Date: Fri, 26 Jul 2019 08:01:16 -0700 [thread overview]
Message-ID: <20190726080116.68d766a3@hermes.lan> (raw)
In-Reply-To: <06bb50da-e56f-3bf0-920f-001480150f5d@intel.com>
On Fri, 26 Jul 2019 10:53:58 +0100
"Burakov, Anatoly" <anatoly.burakov@intel.com> wrote:
> >
> > NP to disallow it.
> > In fact, I think it would be easier for everyone just to drop current DPDK MP model,
> > and keep just standalone DPDK instances.
>
> That's the dream, but i don't think it'll ever come to fruition, at
> least not without a huge push from the community.
There are several net appliances that require primary/secondary model.
I think initially during DPDK development it was sold as a feature to the
Network vendors.
It might be possible to clamp down on what API's are supported by
secondary process. For example, disallowing any control operations start/stop etc.
next prev parent reply other threads:[~2019-07-26 15:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 9:05 [dpdk-dev] Should we disallow running secondaries after primary has died? Burakov, Anatoly
2019-07-26 9:39 ` Bruce Richardson
2019-07-26 9:50 ` Ananyev, Konstantin
2019-07-26 9:53 ` Burakov, Anatoly
2019-07-26 15:01 ` Stephen Hemminger [this message]
2019-07-26 15:44 ` Burakov, Anatoly
2019-07-26 15:56 ` Lipiec, Herakliusz
2019-07-26 16:02 ` Burakov, Anatoly
2019-07-26 16:44 ` Lipiec, Herakliusz
2019-07-26 16:57 ` Burakov, Anatoly
2019-07-26 17:33 ` Lipiec, Herakliusz
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=20190726080116.68d766a3@hermes.lan \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=thomas@monjalon.net \
/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.