netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: netdev@vger.kernel.org, shemminger@linux-foundation.org,
	davem@davemloft.net, jeff@garzik.org
Subject: Re: [RFC NET 00/02]: Secondary unicast address support
Date: Thu, 21 Jun 2007 21:13:37 +0200	[thread overview]
Message-ID: <467ACDE1.7070907@trash.net> (raw)
In-Reply-To: <m13b0lf7mr.fsf@ebiederm.dsl.xmission.com>

Eric W. Biederman wrote:
> I'm trying to understand what the point of this patch is.
>
> In once sense I find the concept of filtering and listening for multiple
> mac addresses very interesting, especially if we could break out different
> streams of traffic by destination mac address into separate network devices.
> This would remove the need to any kind of ethernet tunnel and makes multiple
> network namespaces much more pleasant.
>
> However this just seems to allow a card to decode multiple mac addresses
> which in some oddball load balancing configurations may actually be
> useful, but it seems fairly limited.
>
> Do you have a specific use case you envision for this multiple mac
> functionality?
>   

Yes, please see the MACVLAN patch I posted one or two days earlier.
8021q can also make use of it and Dave mentioned some virtualization
devices want this as well.



  parent reply	other threads:[~2007-06-21 19:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-20 18:00 [RFC NET 00/02]: Secondary unicast address support Patrick McHardy
2007-06-20 18:00 ` [RFC NET 01/02]: " Patrick McHardy
2007-06-20 18:00 ` [RFC E1000 02/02]: " Patrick McHardy
2007-06-21 19:08 ` [RFC NET 00/02]: " Eric W. Biederman
2007-06-21 19:13   ` David Miller
2007-06-21 21:11     ` Caitlin Bestler
2007-06-21 19:13   ` Patrick McHardy [this message]
2007-06-21 20:31     ` Eric W. Biederman
2007-06-22  0:08       ` Patrick McHardy
2007-06-22  3:30         ` Ben Greear
2007-06-22  4:30           ` Eric W. Biederman
2007-06-22 12:08             ` Ben Greear
2007-06-22  1:56       ` Patrick McHardy
2007-06-22  3:21         ` Ben Greear
2007-06-22 11:36           ` Patrick McHardy

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=467ACDE1.7070907@trash.net \
    --to=kaber@trash.net \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.com \
    --cc=jeff@garzik.org \
    --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).