Thread (21 messages) 21 messages, 5 authors, 2009-11-30

Re: [RFC PATCH 1/4] net: Add support to netdev ops for changing hardware queue MAC and VLAN filters

From: Simon Horman <horms@verge.net.au>
Date: 2009-11-30 06:03:18

On Mon, Nov 23, 2009 at 12:52:48PM -0700, Williams, Mitch A wrote:
quoted
From: Ben Hutchings [mailto:bhutchings@solarflare.com]
Sent: Monday, November 23, 2009 5:23 AM
[snip]
quoted
How does this interact with use of multiple queues within a single
function?  Are the specified queue numbers really interpreted as RX
queue indices or as function numbers?

Ben.
Yeah, that is ambiguous.  Would it be better if we changed the name of the parameter to 'vf' instead of 'queue' to make it explicit?

This would give us:
$ ip link set eth1 vf 1 mac <blah>

The issue of which VF goes with which PF device can be deduced in
userspace via sysfs.
Does this mean that the configuration of filtering for a VF needs
to be done where the interface for the VF exists - e.g. in a KVM
guest/Xen domU?

In terms of dealing with interfaces and the way that tools such as ip work
that makes a lot of sense. But I wonder if it actually makes more sense
from an administrative point of view to have this configuration go through
the PF - e.g. the KVM host/Xen domO.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help