From: Andrew Lunn <andrew@lunn.ch>
To: Ran Shalit <ranshalit@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: cascaded switch
Date: Fri, 18 May 2018 22:51:29 +0200 [thread overview]
Message-ID: <20180518205129.GJ23100@lunn.ch> (raw)
In-Reply-To: <CAJ2oMh+ciCMb_thn5TV9n_N+mgcUj49sg+4m9O6BOVjpYLEVdg@mail.gmail.com>
> So, it is used so that the 2 switch will behave as if it is one big switch.
Yes. This particularly important with offloading. When your offload a
bridge, you don't need to care which switch the ports or on. If
traffic needs to go from one switch to the other, it will. If you
modelled it as two switches, you would need to manually setup that
cross switch connection.
Andrew
prev parent reply other threads:[~2018-05-18 20:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 18:35 cascaded switch Ran Shalit
2018-05-18 19:13 ` Andrew Lunn
2018-05-18 20:10 ` Ran Shalit
2018-05-18 20:29 ` Andrew Lunn
2018-05-18 20:40 ` Ran Shalit
2018-05-18 20:51 ` Andrew Lunn [this message]
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=20180518205129.GJ23100@lunn.ch \
--to=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
--cc=ranshalit@gmail.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