[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 08 Sep 2011 20:00:53 -0700
From: Roopa Prabhu <roprabhu@...co.com>
To: "Michael S. Tsirkin" <mst@...hat.com>
CC: Sridhar Samudrala <sri@...ibm.com>, <netdev@...r.kernel.org>,
<dragos.tatulea@...il.com>, <arnd@...db.de>, <dwang2@...co.com>,
<benve@...co.com>, <kaber@...sh.net>, <davem@...emloft.net>,
<eric.dumazet@...il.com>, <mchan@...adcom.com>,
<kvm@...r.kernel.org>
Subject: Re: [net-next-2.6 PATCH 0/3 RFC] macvlan: MAC Address filtering
support for passthru mode
On 9/8/11 12:33 PM, "Michael S. Tsirkin" <mst@...hat.com> wrote:
> On Thu, Sep 08, 2011 at 12:23:56PM -0700, Roopa Prabhu wrote:
>>>
>>> I think the main usecase for passthru mode is to assign a SR-IOV VF to
>>> a single guest.
>>>
>> Yes and for the passthru usecase this patch should be enough to enable
>> filtering in hw (eventually like I indicated before I need to fix vlan
>> filtering too).
>
> So with filtering in hw, and in sriov VF case, VFs
> actually share a filtering table. How will that
> be partitioned?
AFAIK, though it might maintain a single filter table space in hw, hw does
know which filter belongs to which VF. And the OS driver does not need to do
anything special. The VF driver exposes a VF netdev. And any uc/mc addresses
registered with a VF netdev are registered with the hw by the driver. And hw
will filter and send only pkts that the VF has expressed interest in.
No special filter partitioning in hw is required.
Thanks,
Roopa
--
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