From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com,
pablo.de.lara.guarch@intel.com, john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH v2 0/2] examples/l2fwd: Add option to enable/disable MAC addresses updating
Date: Thu, 13 Oct 2016 09:26:03 +0200 [thread overview]
Message-ID: <3683447.M4Gzv30DBN@xps13> (raw)
In-Reply-To: <1474638654-26919-1-git-send-email-maxime.coquelin@redhat.com>
2016-09-23 15:50, Maxime Coquelin:
> This series adds a new option to enable/disable MAC addresses updating in
> l2fwd example.
>
> Doing that, we can enable basic VM 2 VM communication easily, without
> external projects dependencies, nor real NIC (as with vhost example).
>
> Example of cli with vhost-user:
>
> #l2fwd -c f --socket-mem=1024 \
> --vdev 'eth_vhost0,iface=/tmp/vhost-user1,queues=1' \
> --vdev 'eth_vhost1,iface=/tmp/vhost-user2,queues=1' \
> -- -p3 --no-mac-updating
>
> By default, MAC addresses updating remains enabled, but maybe we could
> consider having it disabled by default to be consistent with l2fwd-cat
> for example.
Applied (as a single patch), thanks
prev parent reply other threads:[~2016-10-13 7:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 13:50 Maxime Coquelin
2016-09-23 13:50 ` [dpdk-dev] [PATCH v2 1/2] examples/l2fwd: Add new " Maxime Coquelin
2016-09-23 13:50 ` [dpdk-dev] [PATCH v2 2/2] doc: l2fwd: document new --[no-]mac-updating option Maxime Coquelin
2016-09-26 10:33 ` Mcnamara, John
2016-09-26 15:36 ` Mcnamara, John
2016-09-26 15:40 ` Maxime Coquelin
2016-10-13 7:26 ` 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=3683447.M4Gzv30DBN@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=maxime.coquelin@redhat.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).