From: John Default <default@advaita.sytes.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Layer 3 switching...
Date: Fri, 05 Oct 2007 10:05:35 +0000 [thread overview]
Message-ID: <47060C6F.1040704@advaita.sytes.net> (raw)
In-Reply-To: <4705538C.7070403@riverviewtech.net>
Hi
I was told that layer 3 switches are faster because "routing" there is
done by some ASIC hardware. Is there any advantage in having another
routing code in bridging when everything is done in software which is
same slow as normal routing? The only speed gain would be in keeping the
routing code very simple with limited functionality, but i think that
the trend is to put there more and more functionality which would end up
in having two same slow, same function code in two places.
(i was taugth that packets are routed on L3, frames are
switched(bridged) on L2. And L3 switch does L2 switching + L3 routing
but in hardware. routers are completely a software thing, switches
hardware thing, and bridge is switch in software.)
Please excuse me if i am missing your idea completely.
Grant Taylor wrote:
> Is it even possible or even worth while to do layer 3 switching
> (bridging) on a Linux system?
>
> Or would this be considered routing even though everything is done on
> OSI Layer 2?
>
> Which would be faster, Layer 3 switching (bridging) on OSI Layer 2 or
> routing on OSI Layer 3?
>
>
>
> Grant. . . .
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
--
___________________________________
S pozdravom / Best regards
John Default
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-10-05 10:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 20:56 [LARTC] Layer 3 switching Grant Taylor
2007-10-05 10:05 ` John Default [this message]
2007-10-05 14:48 ` Grant Taylor
2007-10-06 11:16 ` John Default
2007-10-06 12:39 ` Mohan Sundaram
2007-10-08 14:48 ` Grant Taylor
2007-10-08 15:00 ` Grant Taylor
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=47060C6F.1040704@advaita.sytes.net \
--to=default@advaita.sytes.net \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.