From: "Padam J. Singh" <padam.singh@inventum.net>
To: "Zhang, Helin" <helin.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] KNI hw Address.
Date: Thu, 3 Jul 2014 10:35:30 +0530 [thread overview]
Message-ID: <AC395003-9317-49E8-81E2-1B39195E7244@inventum.net> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A74A0DD@SHSMSX104.ccr.corp.intel.com>
Zhang, Alex,
Please see the patch I had submitted a few days back which allows setting the MAC address using
ifconfig ... hw ether MAC-ADDRESS
An "ifconfig DEV up" , followed by this sets the MAC address.
Thanks,
Padam
On 03-Jul-2014, at 10:26 am, Zhang, Helin <helin.zhang@intel.com> wrote:
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Alex Markuze
>> Sent: Wednesday, July 2, 2014 11:57 PM
>> To: dev@dpdk.org
>> Subject: [dpdk-dev] KNI hw Address.
>>
>> Hi, I'm playing with KNI on a VM (kvm), the Interface that is created has no
>> MAC address until the IP is set via ifconfig - then a random mac is created.
>> The VF has a mac address that is easily retrieved with rte_eth_macaddr_get.
>>
>> What I did not find is a way to create the KNI with that specific mac address
>> enabled.
>> What are the ways to set the KNI mac address?
>>
>> Thanks
>> Alex
>
> Hi Alex
>
> No way without modifying the code. Two ways can be taken into account as below.
>
> 1. Implement ndo_set_mac in KNI kernel module to set the MAC address.
> 2. Add mac address as one more parameters in user space KNI interface, to tell the kernel module the mac during kni device creation.
>
> Regards,
> Helin
next prev parent reply other threads:[~2014-07-03 5:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 15:57 Alex Markuze
2014-07-03 4:56 ` Zhang, Helin
2014-07-03 5:05 ` Padam J. Singh [this message]
2014-07-03 6:22 ` Zhang, Helin
2014-07-03 7:06 ` Alex Markuze
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=AC395003-9317-49E8-81E2-1B39195E7244@inventum.net \
--to=padam.singh@inventum.net \
--cc=dev@dpdk.org \
--cc=helin.zhang@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).