DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Gage Eads <gage.eads@intel.com>
Cc: dev@dpdk.org, anatoly.burakov@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] examples/multi_process: remove l2fwd fork example
Date: Sun, 05 Aug 2018 21:46:54 +0200	[thread overview]
Message-ID: <1873240.te3u2aWeyU@xps> (raw)
In-Reply-To: <20180730151000.23024-1-gage.eads@intel.com>

30/07/2018 17:10, Gage Eads:
> 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.
> 
> This patch was made following this mailing list discussion:
> http://mails.dpdk.org/archives/dev/2018-July/108106.html
> 
> Signed-off-by: Gage Eads <gage.eads@intel.com>

Applied, thanks

      reply	other threads:[~2018-08-05 19:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-27 18:56 [dpdk-dev] [PATCH] " Gage Eads
2018-07-30  8:52 ` Burakov, Anatoly
2018-07-30 15:05   ` Eads, Gage
2018-07-30 15:10 ` [dpdk-dev] [PATCH v2] " Gage Eads
2018-08-05 19:46   ` 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=1873240.te3u2aWeyU@xps \
    --to=thomas@monjalon.net \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=gage.eads@intel.com \
    /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).