From: Vladimir Oltean <olteanv@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
netdev@vger.kernel.org, andrew@lunn.ch, vivien.didelot@gmail.com,
Hauke Mehrtens <hauke@hauke-m.de>,
Aleksander Jan Bajkowski <olek2@wp.pl>
Subject: Re: net: dsa: lantiq_gswip: getting the first selftests to pass
Date: Thu, 28 Jul 2022 03:02:30 +0300 [thread overview]
Message-ID: <20220728000230.kfwd5rkn433f2ecf@skbuf> (raw)
In-Reply-To: <7dba0e0b-b3d8-a40e-23dd-3cc7999b8fc4@gmail.com>
On Wed, Jul 27, 2022 at 02:07:51PM -0700, Florian Fainelli wrote:
> Since I am in the process of re-designing my test rack at home with
> DSA devices, how do you run the selftests out of curiosity? Is there a
> nice diagram that explains how to get a physical connection set-up?
>
> I used to have between 2 and 4 Ethernet controllers dedicated to each
> port of the switch of the DUT so I could run
> bridge/standalone/bandwidth testing but I feel like this is a tad
> extreme and am cutting down on the number of Ethernet ports so I can
> put NVMe drives in the machine instead.
tools/testing/selftests/net/forwarding/README
br0
+
vrf-h1 | vrf-h2
+ +---+----+ +
| | | |
192.0.2.1/24 + + + + 192.0.2.2/24
swp1 swp2 swp3 swp4
+ + + +
| | | |
+--------+ +--------+
Most of the tests assume these 4 ports, otherwise the topology is
mentioned in a drawing for that particular selftest.
The names used by the tests are actually $h1 and $h2 for the host ports
(extreme left and extreme right) - these terminate traffic - and $swp1
and $swp2 (mid left and mid right) - these forward traffic. In the
drawing from the README, I suppose the names "swp1 ... swp4" were used
to illustrate that you can use switch net devices as host ports, and
also as forwarding ports.
next prev parent reply other threads:[~2022-07-28 0:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 20:36 net: dsa: lantiq_gswip: getting the first selftests to pass Martin Blumenstingl
2022-07-27 21:07 ` Florian Fainelli
2022-07-28 0:02 ` Vladimir Oltean [this message]
2022-07-28 22:30 ` Florian Fainelli
2022-07-27 22:44 ` Vladimir Oltean
2022-07-28 22:09 ` Martin Blumenstingl
2022-07-29 0:05 ` Vladimir Oltean
2022-07-31 20:49 ` Martin Blumenstingl
2022-07-31 21:29 ` Aleksander Bajkowski
2022-08-01 19:48 ` Martin Blumenstingl
2022-08-03 15:54 ` Vladimir Oltean
2022-08-03 22:02 ` Hauke Mehrtens
2022-08-03 21:50 ` Hauke Mehrtens
2022-08-03 21:51 ` Hauke Mehrtens
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=20220728000230.kfwd5rkn433f2ecf@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=martin.blumenstingl@googlemail.com \
--cc=netdev@vger.kernel.org \
--cc=olek2@wp.pl \
--cc=vivien.didelot@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