> -----Original Message----- > From: netdev-owner@xxxxxxxxxxxxxxx [mailto:netdev-owner@xxxxxxxxxxxxxxx] > On Behalf Of Roopa Prabhu > Sent: Monday, October 24, 2011 11:15 AM > To: Michael S. Tsirkin > Cc: netdev@xxxxxxxxxxxxxxx; sri@xxxxxxxxxx; dragos.tatulea@xxxxxxxxx; > arnd@xxxxxxxx; kvm@xxxxxxxxxxxxxxx; davem@xxxxxxxxxxxxx; > mchan@xxxxxxxxxxxx; dwang2@xxxxxxxxx; shemminger@xxxxxxxxxx; > eric.dumazet@xxxxxxxxx; kaber@xxxxxxxxx; benve@xxxxxxxxx; Rose, Gregory V > Subject: Re: [net-next-2.6 PATCH 0/8 RFC v2] macvlan: MAC Address > filtering support for passthru mode > > On 10/23/11 10:47 PM, "Michael S. Tsirkin" <mst@xxxxxxxxxx> wrote: > > >> AFAIK, there is no netdev interface to install per queue hw > >> filters for a multi queue interface. And also I dont know of any hw > >> that provides an interface to set hw filters on a per queue basis. > > > > VMDq hardware would support this, no? > > > Am not really sure. This patch uses netdev to pass filters to hw. And I > don't see any netdev infrastructure that would support per queue filters. > Maybe Greg (CC'ed) or anyone else from Intel can answer this. > Greg, michael had brought up this question during first version of these > patches as well. Will be nice to get the VMDq requirements for propagating > guest filters to hw clarified. Do you see any special VMDq nic requirement > we can cover in this patch. This is for VMDq queues directly connected to > guest nics. Thanks. So far as I know there is no support for VMDq in the Linux kernel and while I know some folks have been working on it I can't really speak to that work or their plans. Much would depend on the implementation. For now it makes sense to me to get support for multiple MAC and VLAN filters per virtual function (or virtual nic) and it seems to me you're going in the right direction for this. We'll have a look at your next set of patches and take it from there. - Greg -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
