From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: jeffrey.t.kirsher@intel.com, netdev@vger.kernel.org,
gospo@redhat.com, mitch.a.williams@intel.com
Subject: Re: [RFC PATCH iproute2] ip: Add support for setting MAC and VLAN on hardware queues
Date: Wed, 18 Nov 2009 10:07:28 -0800 (PST) [thread overview]
Message-ID: <20091118.100728.91511216.davem@davemloft.net> (raw)
In-Reply-To: <20091117140641.7f8c8ac0@nehalam>
From: Stephen Hemminger <shemminger@vyatta.com>
Date: Tue, 17 Nov 2009 14:06:41 -0800
> On Tue, 17 Nov 2009 13:55:07 -0800
> Jeff Kirsher <jeffrey.t.kirsher@intel.com> wrote:
>
>> From: Williams, Mitch A <mitch.a.williams@intel.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@intel.com>
>> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.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.
next prev parent reply other threads:[~2009-11-18 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 21:55 [RFC PATCH iproute2] ip: Add support for setting MAC and VLAN on hardware queues Jeff Kirsher
2009-11-17 22:06 ` Stephen Hemminger
2009-11-18 18:07 ` David Miller [this message]
2009-11-18 19:15 ` Stephen Hemminger
2009-11-18 22:07 ` Williams, Mitch A
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=20091118.100728.91511216.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=mitch.a.williams@intel.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).