[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091130060323.GA17989@verge.net.au>
Date: Mon, 30 Nov 2009 17:03:23 +1100
From: Simon Horman <horms@...ge.net.au>
To: "Williams, Mitch A" <mitch.a.williams@...el.com>
Cc: Ben Hutchings <bhutchings@...arflare.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"shemminger@...tta.com" <shemminger@...tta.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"gospo@...hat.com" <gospo@...hat.com>
Subject: Re: [RFC PATCH 1/4] net: Add support to netdev ops for changing
hardware queue MAC and VLAN filters
On Mon, Nov 23, 2009 at 12:52:48PM -0700, Williams, Mitch A wrote:
> >From: Ben Hutchings [mailto:bhutchings@...arflare.com]
> >Sent: Monday, November 23, 2009 5:23 AM
> [snip]
>
> >
> >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.
--
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