From: "Eads, Gage" <gage.eads@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] examples/multi_process: remove l2fwd fork example
Date: Mon, 30 Jul 2018 15:05:42 +0000 [thread overview]
Message-ID: <9184057F7FC11744A2107296B6B8EB1E446F55FB@FMSMSX108.amr.corp.intel.com> (raw)
In-Reply-To: <dbcef9c9-af2e-b29b-5c1b-fbf143e8c427@intel.com>
> -----Original Message-----
> From: Burakov, Anatoly
> Sent: Monday, July 30, 2018 3:53 AM
> To: Eads, Gage <gage.eads@intel.com>; dev@dpdk.org
> Subject: Re: [PATCH] examples/multi_process: remove l2fwd fork example
>
> On 27-Jul-18 7:56 PM, Gage Eads wrote:
> > l2fwd_fork relies on a multiprocess model that that DPDK does not
> > support (calling rte_eal_init() before fork()), in particular in light
> > of recent EAL changes like the multiproess communication channel.
> >
> > This example can mislead users into thinking this is a supported
> > multiprocess model; hence, this commit removes this example and the
> > corresponding user guide documentation as well.
> >
> > Signed-off-by: Gage Eads <gage.eads@intel.com>
> > ---
>
> Hi Gage,
>
> Maybe the commit message should reference the earlier discussion on the
> mailing list.
Certainly, will do.
Thanks,
Gage
>
> --
> Thanks,
> Anatoly
next prev parent reply other threads:[~2018-07-30 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 18:56 Gage Eads
2018-07-30 8:52 ` Burakov, Anatoly
2018-07-30 15:05 ` Eads, Gage [this message]
2018-07-30 15:10 ` [dpdk-dev] [PATCH v2] " Gage Eads
2018-08-05 19:46 ` Thomas Monjalon
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=9184057F7FC11744A2107296B6B8EB1E446F55FB@FMSMSX108.amr.corp.intel.com \
--to=gage.eads@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@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 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).