From: Jeff Garzik <jeff@garzik.org>
To: David Miller <davem@davemloft.net>, kaber@trash.net
Cc: shemminger@linux-foundation.org, netdev@vger.kernel.org
Subject: Re: [NET 00/02]: MACVLAN driver
Date: Wed, 20 Jun 2007 02:34:39 -0400 [thread overview]
Message-ID: <4678CA7F.8070002@garzik.org> (raw)
In-Reply-To: <20070619.154840.55744015.davem@davemloft.net>
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
next prev parent reply other threads:[~2007-06-20 6:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 13:08 [NET 00/02]: MACVLAN driver Patrick McHardy
2007-06-19 13:08 ` [ETHERNET 01/02]: Validate new address in eth_mac_addr Patrick McHardy
2007-06-19 13:08 ` [NET 02/02]: Add MACVLAN driver Patrick McHardy
2007-06-19 16:00 ` [NET 00/02]: " Stephen Hemminger
2007-06-19 19:53 ` Chris Leech
2007-06-19 21:14 ` Patrick McHardy
2007-06-19 22:29 ` Stephen Hemminger
2007-06-19 22:48 ` David Miller
2007-06-19 23:44 ` Patrick McHardy
2007-06-20 6:34 ` Jeff Garzik [this message]
2007-06-20 19:35 ` Prafulla Deuskar
2007-06-21 14:57 ` Patrick McHardy
-- strict thread matches above, loose matches on Subject: below --
2007-06-24 4:52 Mark Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4678CA7F.8070002@garzik.org \
--to=jeff@garzik.org \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).