DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/2] examples/l2fwd: Add option to enable/disable	MAC addresses tweaking
Date: Tue, 30 Aug 2016 15:42:26 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2025D8AE6@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1469548587-3202-1-git-send-email-maxime.coquelin@redhat.com>

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Maxime Coquelin
> Sent: Tuesday, July 26, 2016 4:56 PM
> To: Richardson, Bruce <bruce.richardson@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>
> Cc: dev@dpdk.org; Maxime Coquelin <maxime.coquelin@redhat.com>
> Subject: [dpdk-dev] [PATCH 0/2] examples/l2fwd: Add option to
> enable/disable MAC addresses tweaking
> 
> This series adds a new option to enable/disable MAC addresses tweaking 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).

Hi,

This looks like a useful feature. However, I don't know if "tweaking" is
the best description of the feature. Maybe "updating" would be better.

John

  parent reply	other threads:[~2016-08-30 15:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26 15:56 Maxime Coquelin
2016-07-26 15:56 ` [dpdk-dev] [PATCH 1/2] examples/l2fwd: Add new " Maxime Coquelin
2016-08-30 15:42   ` Mcnamara, John
2016-07-26 15:56 ` [dpdk-dev] [PATCH 2/2] doc: l2fwd: document new --[no-]mac-tweaking option Maxime Coquelin
2016-08-30 15:42 ` Mcnamara, John [this message]
2016-09-23 13:54   ` [dpdk-dev] [PATCH 0/2] examples/l2fwd: Add option to enable/disable MAC addresses tweaking Maxime Coquelin
2016-09-21 21:53 ` De Lara Guarch, Pablo
2016-09-23 13:52   ` Maxime Coquelin
2016-09-23 17:11     ` De Lara Guarch, Pablo

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=B27915DBBA3421428155699D51E4CFE2025D8AE6@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --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).