netdev - Re: [NET 00/02]: MACVLAN driver

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 20 Jun 2007 12:35:59 -0700
From:	"Prafulla Deuskar" <pdeuskar01@...il.com>
To:	"Jeff Garzik" <jeff@...zik.org>
Cc:	"David Miller" <davem@...emloft.net>, kaber@...sh.net,
	shemminger@...ux-foundation.org, netdev@...r.kernel.org
Subject: Re: [NET 00/02]: MACVLAN driver

On 6/19/07, Jeff Garzik <jeff@...zik.org> wrote:
> David Miller wrote:
> > This is actually a real issue for virtualization, and many
> > if not all current generation ethernet chips support
> > programming several unicast ethernet addresses in the MAC.
> >
> > Networking switches in domain0 on virtualization hosts use
> > this feature to support seperate MACs per guest node,
> > and if the chip doesn't support this the chip is put into
> > promiscuous mode.
> >
> > We don't have any clean interfaces by which to do this MAC
> > programming, and we do need something for it soon.
>
>
> Yep, that's been on my long term wish list for a while, as well.
>
> Overall I would like to see a more flexible way of allowing the net
> stack to learn each NIC's RX filter capabilities, and exploiting them.
> Plenty of NICs, even 100Mbps ones, support RX filter management that
> allows scanning for $hw_limit unicast addresses, before having to put
> the hardware into promisc mode.
>
>        Jeff

So how do we manage mac address to RX queue association?
Ideally we should extend ethtool to do that rather than inventing a
new tool - Is that acceptable?

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