From: "Paul Congdon \(UC Davis\)" <ptcongdon@ucdavis.edu>
To: "'Stephen Hemminger'" <shemminger@vyatta.com>
Cc: <drobbins@funtoo.org>, "'Fischer, Anna'" <anna.fischer@hp.com>,
"'Arnd Bergmann'" <arnd@arndb.de>, <herbert@gondor.apana.org.au>,
<mst@redhat.com>, <netdev@vger.kernel.org>,
<bridge@lists.linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <ogerlitz@voltaire.com>,
<evb@yahoogroups.com>, <davem@davemloft.net>
Subject: RE: [Bridge] [PATCH] macvlan: add tap device backend
Date: Fri, 7 Aug 2009 12:47:38 -0700 [thread overview]
Message-ID: <005601ca1797$ef5dc180$ce194480$@edu> (raw)
In-Reply-To: <20090807123554.7c2bc27c@nehalam>
>
> I do have to raise the point that Linux is perfectly capable of keeping
> up without
> the need of an external switch. Whether you want policy external or
> internal is
> a architecture decision that should not be driven by mis-information
> about performance.
No argument here. I agree that you can do a lot in Linux. It is, as you
say, an architecture decision, that can be enabled with this addition mode
of operation. Without the mode of forcing things external, however, you
would always need to put this function internal or play games with VLANs
overlapping to get traffic to forward the way you want it.
Paul
next prev parent reply other threads:[~2009-08-07 19:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0199E0D51A61344794750DC57738F58E6D6A6CD7F6@GVW1118EXC.americas.hpqcorp.net>
2009-08-07 19:10 ` [Bridge] [PATCH] macvlan: add tap device backend Paul Congdon (UC Davis)
2009-08-07 19:35 ` Stephen Hemminger
2009-08-07 19:44 ` Fischer, Anna
2009-08-07 20:17 ` david
2009-08-07 19:47 ` Paul Congdon (UC Davis) [this message]
2009-08-07 21:38 ` Arnd Bergmann
2009-08-07 22:05 ` Arnd Bergmann
2009-08-10 12:40 ` Fischer, Anna
2009-08-10 19:04 ` Arnd Bergmann
2009-08-10 19:32 ` Michael S. Tsirkin
2009-08-06 21:50 Arnd Bergmann
2009-08-07 17:35 ` [Bridge] " Daniel Robbins
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='005601ca1797$ef5dc180$ce194480$@edu' \
--to=ptcongdon@ucdavis.edu \
--cc=anna.fischer@hp.com \
--cc=arnd@arndb.de \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=drobbins@funtoo.org \
--cc=evb@yahoogroups.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@voltaire.com \
--cc=shemminger@vyatta.com \
/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).