Re: [NET 00/02]: MACVLAN driver

[Patrick McHardy <kaber@trash.net>]

Prafulla Deuskar wrote:
> On 6/19/07, Jeff Garzik <jeff@garzik.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? 


This is not about multiple RX queues but filtering multiple unicast
addresses without going to promiscous mode. The addresses are used
by something outside the driver, like macvlan.