From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Andrey Chilikin <andrey.chilikin@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] l3fwd: make destination mac address configurable
Date: Wed, 03 Jun 2015 10:18:24 +0200 [thread overview]
Message-ID: <4167173.t9b6F3TTVr@xps13> (raw)
In-Reply-To: <1431951204-14148-1-git-send-email-andrey.chilikin@intel.com>
2015-05-18 13:13, Andrey Chilikin:
> Add a command-line parameter to l3fwd, to allow the user to specify the destination mac address for each ethernet port used.
>
> v2 changes:
> - apply command-line parameter to fast path as well (val_eth)
>
> Signed-off-by: Andrey Chilikin <andrey.chilikin@intel.com>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Applied, thanks
prev parent reply other threads:[~2015-06-03 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 13:16 [dpdk-dev] [PATCH] " Bruce Richardson
2015-05-12 14:42 ` Ananyev, Konstantin
2015-05-18 12:13 ` [dpdk-dev] [PATCH v2] " Andrey Chilikin
2015-06-03 8:18 ` 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=4167173.t9b6F3TTVr@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=andrey.chilikin@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).