netdev - Re: [PATCH 2/2][RFC] virtio_net: Add MAC fitler table support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 10 Jan 2009 13:41:28 -0600
From:	Anthony Liguori <anthony@...emonkey.ws>
To:	Alex Williamson <alex.williamson@...com>
CC:	Rusty Russell <rusty@...tcorp.com.au>, kvm <kvm@...r.kernel.org>,
	netdev <netdev@...r.kernel.org>,
	Mark McLoughlin <markmc@...hat.com>
Subject: Re: [PATCH 2/2][RFC] virtio_net: Add MAC fitler table support

Alex Williamson wrote:
> Hmm, that's not quite how I was implementing it.  The uc_list and
> mc_list are stored up in the netdev level, so there's not much point in
> duplicating it in the guest virtio-net driver.  The interface I was
> working on has two commands.  The first tells the host to allocate the
> MAC filter table for a guest provided number of entries (perhaps a
> module parameter, with reasonable default).  The other is a set command
> with an sg entry providing a buffer of all the MAC entries for the
> table.  If sg entries are no more than a page, this limits us to ~680
> MAC table entries, which I think is far more than any piece of real
> hardware (and large enough that you'd probably want to turn on
> promiscuous already).

Yeah, this is what I would have done although maybe it's worth allowing 
a partial update of the filter table.  Once you're using a command 
interface, a protocol like you describe makes sense.  I was simply going 
the through the logic that led me to suggest a command interface in the 
first place.

>   The VLAN equivalent is a bit easier since by
> definition there are 4k possible VLANs.  There I think a set bit/clear
> bit message interface is appropriate (and maybe a clear all for a reset
> condition).  Let me know if that sounds reasonable.  Thanks,
>   

Yeah, sounds reasonable to me.

Regards,

Anthony Liguori

> Alex
>
>   

--
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