From: Ido Schimmel <idosch@idosch.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Ido Schimmel <idosch@mellanox.com>,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
davem@davemloft.net, shuah@kernel.org, dsahern@gmail.com,
nikolay@cumulusnetworks.com, roopa@cumulusnetworks.com,
andy@greyhouse.net, jiri@mellanox.com, mlxsw@mellanox.com,
saeedm@mellanox.com, tariqt@mellanox.com, jhs@mojatatu.com,
lucasb@mojatatu.com, f.fainelli@gmail.com,
vivien.didelot@savoirfairelinux.com,
jakub.kicinski@netronome.com, simon.horman@netronome.com
Subject: Re: [RFC PATCH net-next 02/12] selftests: forwarding: Add a test for FDB learning
Date: Mon, 15 Jan 2018 22:05:20 +0200 [thread overview]
Message-ID: <20180115200520.GA27952@splinter> (raw)
In-Reply-To: <20180115194146.GA31030@lunn.ch>
Hi Andrew,
On Mon, Jan 15, 2018 at 08:41:46PM +0100, Andrew Lunn wrote:
> On Mon, Jan 15, 2018 at 09:18:43PM +0200, Ido Schimmel wrote:
> > Send a packet with a specific destination MAC, make sure it was learned
> > on the ingress port and then aged-out.
>
> It would be interesting to show the hardware actually uses the FDB,
> not just learns it. Send some packets back, and ensure they go out the
> intended port. Also, check they don't go out a third port, i.e. make
> sure the hardware is not flooding. Once it has aged-out, then test is
> is flooding out all ports.
Good idea. We can actually do that with only two ports. Disable flooding
on port A, check packets with DMAC A don't egress the port. Inject a
packet with SMAC A through port A, check packets with DMAC A egress the
port.
next prev parent reply other threads:[~2018-01-15 20:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 19:18 [RFC PATCH net-next 00/12] selftests: forwarding: Add VRF-based tests Ido Schimmel
2018-01-15 19:18 ` [RFC PATCH net-next 01/12] selftests: forwarding: Add initial testing framework Ido Schimmel
2018-01-17 20:56 ` David Ahern
2018-01-17 21:18 ` Andrew Lunn
2018-01-17 21:26 ` David Ahern
2018-01-15 19:18 ` [RFC PATCH net-next 02/12] selftests: forwarding: Add a test for FDB learning Ido Schimmel
2018-01-15 19:41 ` Andrew Lunn
2018-01-15 20:05 ` Ido Schimmel [this message]
2018-01-15 21:01 ` Andrew Lunn
2018-01-17 20:48 ` David Ahern
2018-01-17 21:01 ` Jiri Pirko
2018-01-17 22:46 ` Roopa Prabhu
2018-01-17 22:59 ` Roopa Prabhu
2018-01-17 23:31 ` Jiri Pirko
2018-01-18 0:15 ` David Ahern
2018-01-18 7:16 ` Ido Schimmel
2018-01-18 7:51 ` Jiri Pirko
2018-01-15 19:18 ` [RFC PATCH net-next 03/12] selftests: forwarding: Add a test for flooded traffic Ido Schimmel
2018-01-15 19:18 ` [RFC PATCH net-next 04/12] selftests: forwarding: Add a test for basic IPv4 and IPv6 routing Ido Schimmel
2018-01-15 19:18 ` [RFC PATCH net-next 05/12] selftests: forwarding: Create test topology for multipath routing Ido Schimmel
2018-01-15 19:18 ` [RFC PATCH net-next 06/12] selftests: forwarding: Test IPv4 weighted nexthops Ido Schimmel
2018-01-15 19:18 ` [RFC PATCH net-next 07/12] selftests: forwarding: Test IPv6 " Ido Schimmel
2018-01-15 19:18 ` [RFC PATCH net-next 08/12] selftests: forwarding: Add tc offload check helper Ido Schimmel
2018-01-15 19:18 ` [RFC PATCH net-next 09/12] selftests: forwarding: Add MAC get helper Ido Schimmel
2018-01-15 19:18 ` [RFC PATCH net-next 10/12] selftests: forwarding: Allow to get netdev interfaces names from commandline Ido Schimmel
2018-01-15 19:18 ` [RFC PATCH net-next 11/12] selftests: forwarding: Allow to pass commandline options Ido Schimmel
2018-01-15 19:18 ` [RFC PATCH net-next 12/12] selftests: forwarding: Introduce tc flower matching tests Ido Schimmel
2018-01-15 20:14 ` [RFC PATCH net-next 00/12] selftests: forwarding: Add VRF-based tests David Ahern
2018-01-15 23:17 ` Jiri Pirko
2018-01-15 23:48 ` David Ahern
2018-01-16 7:59 ` Ido Schimmel
2018-01-17 22:51 ` Florian Fainelli
2018-01-17 23:11 ` Andrew Lunn
2018-01-18 7:41 ` Ido Schimmel
2018-01-18 12:46 ` Andrew Lunn
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=20180115200520.GA27952@splinter \
--to=idosch@idosch.org \
--cc=andrew@lunn.ch \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=idosch@mellanox.com \
--cc=jakub.kicinski@netronome.com \
--cc=jhs@mojatatu.com \
--cc=jiri@mellanox.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=lucasb@mojatatu.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
--cc=saeedm@mellanox.com \
--cc=shuah@kernel.org \
--cc=simon.horman@netronome.com \
--cc=tariqt@mellanox.com \
--cc=vivien.didelot@savoirfairelinux.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).