[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20091118.100728.91511216.davem@davemloft.net>
Date: Wed, 18 Nov 2009 10:07:28 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: shemminger@...tta.com
Cc: jeffrey.t.kirsher@...el.com, netdev@...r.kernel.org,
gospo@...hat.com, mitch.a.williams@...el.com
Subject: Re: [RFC PATCH iproute2] ip: Add support for setting MAC and VLAN
on hardware queues
From: Stephen Hemminger <shemminger@...tta.com>
Date: Tue, 17 Nov 2009 14:06:41 -0800
> On Tue, 17 Nov 2009 13:55:07 -0800
> Jeff Kirsher <jeffrey.t.kirsher@...el.com> wrote:
>
>> From: Williams, Mitch A <mitch.a.williams@...el.com>
>>
>> This patch adds support to the "ip" tool for setting the MAC address and
>> VLAN filter for hardware device queues. This is most immediately useful for
>> SR-IOV; for VF devices to be usable in the real world, the hypervisor or VM
>> manager must be able to set these parameters before the VF device is
>> assigned to any VM.
>>
>> Signed-off-by: Mitch Williams <mitch.a.williams@...el.com>
>> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
>
> Is there anything to avoid prevent this from being misused by users who
> are doing multiqueue. Maybe we need equivalent of "mounted" flag that block
> devices have?
It's a privileged config operation as far as I can tell.
Given that, what could we possibly need to protect?
This stuff looks basically fine to me.
--
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