[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK+XE=k9VLsnYVnhVYYmzKO5_GQ1u+hDx6uAFrvm7ziQyJntgw@mail.gmail.com>
Date: Mon, 5 Mar 2018 23:20:11 +0000
From: John Hurley <john.hurley@...ronome.com>
To: Or Gerlitz <gerlitz.or@...il.com>
Cc: Linux Netdev List <netdev@...r.kernel.org>,
Jiri Pirko <jiri@...lanox.com>,
Or Gerlitz <ogerlitz@...lanox.com>,
Jakub Kicinski <jakub.kicinski@...ronome.com>,
Simon Horman <simon.horman@...ronome.com>
Subject: Re: [RFC net-next 4/6] nfp: add ndo_set_mac_address for representors
On Mon, Mar 5, 2018 at 9:39 PM, Or Gerlitz <gerlitz.or@...il.com> wrote:
> On Mon, Mar 5, 2018 at 3:28 PM, John Hurley <john.hurley@...ronome.com> wrote:
>> A representor hardware address does not have any meaning outside of the
>> kernel netdev/networking stack. Thus there is no need for any app specific
>> code for setting a representors hardware address, the default eth_mac_addr
>> is sufficient.
>
> where did you need that? does libvirt attempts to change the mac address or
> it's for bonding to call, worth mentioning the use-case in the change log
Hi Or,
yes, setting the mac is required to add the repr to a linux bond.
I agree, I should add the use case here. Thanks
Powered by blists - more mailing lists