From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "Eads, Gage" <gage.eads@intel.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
Olivier Matz <olivier.matz@6wind.com>
Subject: Re: [dpdk-dev] DPDK and forked processes
Date: Fri, 27 Jul 2018 08:59:50 -0700 [thread overview]
Message-ID: <20180727085950.2e2e0281@xeon-e3> (raw)
In-Reply-To: <7441138.EijKcuSYIv@xps>
On Fri, 27 Jul 2018 17:03:48 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:
> 27/07/2018 15:46, Eads, Gage:
> > As this discussion has broad implications for DPDK, is it a good candidate for a techboard meeting topic?
>
> We can discuss it in techboard, but usually we prefer discussing topics
> whose resolution is not clear.
> In this case, I think everybody agree with Anatoly, isn't it?
I would prefer that decisions like this be done by rough consensus on the mailing list.
As far as applications messing with internals, in reality any application can change
anything. Just don't come crying to DPDK community for help.
next prev parent reply other threads:[~2018-07-27 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 15:00 Eads, Gage
2018-07-16 15:09 ` Burakov, Anatoly
2018-07-27 13:46 ` Eads, Gage
2018-07-27 15:03 ` Thomas Monjalon
2018-07-27 15:59 ` Stephen Hemminger [this message]
2018-07-27 16:46 ` Eads, Gage
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=20180727085950.2e2e0281@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gage.eads@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=konstantin.ananyev@intel.com \
--cc=olivier.matz@6wind.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 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).