netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: on the topic of alternate MAC addresses
Date: Tue, 23 Oct 2007 22:25:05 -0400	[thread overview]
Message-ID: <471EAD01.5030502@garzik.org> (raw)
In-Reply-To: <20071023.180534.59659315.davem@davemloft.net>

David Miller wrote:
> I've been meaning to bring this up.
> 
> A lot of cards that support multiple MAC addresses
> in hardware provide pre-cooked lists of alternate
> MAC addresses.  This is either done via EEPROM,
> NVRAM, or OpenFirmware device properties.
> 
> For example, the Sun Neptune cards can provide an
> array of up to 16 alternate MAC addresses per-port.
> 
> We should provide a way to export these lists to
> userspace.
> 
> Perhaps an ethtool thing, Jeff?
> 
> Once we have this, virtualization implementations can probe for and
> use them.  Currently they have no way to discover these things so
> probably they just generate their own using some algorithm.

hmmmm.  Using ethtool isn't a big deal, but IMO you probably want more 
than just an exported list for the usage you described...  it sounds 
like some sort of reservation system should be used, to note which MAC 
addresses are [not] in use?

Then a virt client -- or anyone who wants multiple unicast addresses for 
whatever reason -- can let other clients to avoid MAC addresses 1, 7, or 
13 (random examples).

	Jeff




  reply	other threads:[~2007-10-24  2:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24  1:05 on the topic of alternate MAC addresses David Miller
2007-10-24  2:25 ` Jeff Garzik [this message]
2007-10-24  2:30   ` Jeff Garzik
2007-10-24  3:22   ` David Miller
2007-10-24  9:28     ` Johannes Berg
2007-10-25 16:14     ` Eric W. Biederman
2007-10-25 17:14       ` Rick Jones
2007-10-25 17:36         ` Eric W. Biederman

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=471EAD01.5030502@garzik.org \
    --to=jeff@garzik.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.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).