[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZOPZLr-QYMfQ6homSvkDfUh+np3q5qbmRNLzBgxyWjk+LONQ@mail.gmail.com>
Date: Wed, 11 Jun 2014 15:43:01 +0300
From: Or Gerlitz <or.gerlitz@...il.com>
To: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Cc: David Miller <davem@...emloft.net>,
Mitch Williams <mitch.a.williams@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"gospo@...hat.com" <gospo@...hat.com>,
"sassmann@...hat.com" <sassmann@...hat.com>,
Jesse Brandeburg <jesse.brandeburg@...el.com>
Subject: Re: [net-next 06/13] i40e: implement anti-spoofing for VFs
On Wed, Jun 11, 2014 at 3:13 PM, Jeff Kirsher
<jeffrey.t.kirsher@...el.com> wrote:
> On Mon, 2014-06-09 at 22:49 +0300, Or Gerlitz wrote:
>> On Mon, Jun 9, 2014 at 11:49 AM, Jeff Kirsher
>> <jeffrey.t.kirsher@...el.com> wrote:
>> > From: Mitch Williams <mitch.a.williams@...el.com>
>> >
>> > Our hardware supports VF antispoofing for both MAC addresses and VLANs.
>> > Enable this feature by default for all VFs
>>
>> What do you expect the HW to do when spoof check is enabled (by
>> default) but the admin didn't configure a MAC address for the VF
>> through the PF? that is the VF is allowed to use what ever MAC they
>> want to?
>>
>> > and implement the netdev op to control it from the command line.
>
> Here is the answer I got:
> If the VF mac address is set within the VM and it is accepted by the PF,
When the admin doesn't configure MAC address for the VM, what logic is
applied by the PF to decide whether or not to accept a VF MAC set by the VM?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists