From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Pascal Mazon <pascal.mazon@6wind.com>, keith.wiles@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] net/tap: add support for fixed mac addresses
Date: Fri, 14 Apr 2017 10:45:58 +0100 [thread overview]
Message-ID: <f8e8466e-d888-b86b-18f6-759914f37e7e@intel.com> (raw)
In-Reply-To: <86a184a05fc3acad99d058e9d917f9829b33007b.1491982126.git.pascal.mazon@6wind.com>
On 4/12/2017 8:30 AM, Pascal Mazon wrote:
> Support for a fixed MAC address for testing with the last octet
> incrementing by one for each interface defined with the new 'mac=fixed'
> string on the --vdev option. The default option is still to randomize
> the MAC address for each tap interface.
>
> Signed-off-by: Keith Wiles <keith.wiles@intel.com>
> Signed-off-by: Pascal Mazon <pascal.mazon@6wind.com>
> Acked-by: Keith Wiles <keith.wiles@intel.com>
> ---
>
> v2:
> - fix spaces instead of tab in front of a return
> - MAC address generation should happen before checking for flower support.
> Otherwise the address could be unset with old kernels.
>
Thanks for the patch, this will be considered for 17.08
next prev parent reply other threads:[~2017-04-14 9:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 18:18 [dpdk-dev] [PATCH] " Keith Wiles
2017-04-11 7:18 ` Pascal Mazon
2017-04-11 8:31 ` Ferruh Yigit
2017-04-11 13:23 ` Wiles, Keith
2017-04-11 13:25 ` Wiles, Keith
2017-04-11 13:39 ` Ferruh Yigit
2017-04-11 13:41 ` Wiles, Keith
2017-04-11 13:54 ` Pascal Mazon
2017-04-11 14:17 ` Wiles, Keith
2017-04-11 15:09 ` Pascal Mazon
2017-04-11 15:38 ` Wiles, Keith
2017-04-11 15:42 ` Wiles, Keith
2017-04-11 15:49 ` Ferruh Yigit
2017-04-11 16:16 ` Wiles, Keith
2017-04-12 7:30 ` [dpdk-dev] [PATCH v2] " Pascal Mazon
2017-04-14 9:45 ` Ferruh Yigit [this message]
2017-05-12 12:24 ` Ferruh Yigit
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=f8e8466e-d888-b86b-18f6-759914f37e7e@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
--cc=pascal.mazon@6wind.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).