From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: dev@dpdk.org, "Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: simplify L3fwd user guide examples
Date: Tue, 17 Jan 2017 16:58:55 +0100 [thread overview]
Message-ID: <3139078.WKzoORsS5l@xps13> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE202689D79@IRSMSX103.ger.corp.intel.com>
> > L3 Forwarding sample app user guides have some inconsistencies between the
> > example command line and the configuration table.
> > Also, they were showing too complicated configuration, using two different
> > NUMA nodes for two ports, which will probably lead to performance drop due
> > to use cross-socket channel.
> >
> > This patch simplifies the configuration of these examples, by using a
> > single NUMA node and a single queue per port.
> >
> > Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
>
> Acked-by: John McNamara <john.mcnamara@intel.com>
Applied, thanks
prev parent reply other threads:[~2017-01-17 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 16:34 Pablo de Lara
2016-12-20 10:31 ` Mcnamara, John
2017-01-17 15:58 ` 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=3139078.WKzoORsS5l@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=pablo.de.lara.guarch@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).