netdev - Re: cascaded switch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180518202920.GI23100@lunn.ch>
Date:   Fri, 18 May 2018 22:29:20 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     Ran Shalit <ranshalit@...il.com>
Cc:     netdev@...r.kernel.org
Subject: Re: cascaded switch

> Hi,
> 
> I mean the same terminology used in marvell's switch.(I don't think
> there is more than one terminology for this, please correct me if
> wrong).
> Anyway, I can see examples how it is done, but I don't understand the
> benefit of this constellation, and why device tree needs to be
> familiar with it.
> 
> <   switch 1  >---port10--------port10- <  switch 2 >
>  | ....|         |                                             | ....|    |
> port 1-9     |                                      port 1-9     |
>                  |                                                        |
>                  |                                                        |
> <cpu>--mdio----------------------------------------------

Your ASCII art is all messed up, but i get what you mean.

This is the D in DSA. You would use this when a single switch does not
have enough ports for your use case. So you use two switches.

You need to tell each switch what links are used to get to other
switches. There is an internal routing table. So you need to describe
these links in device tree.

      Andrew