[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180115200520.GA27952@splinter>
Date: Mon, 15 Jan 2018 22:05:20 +0200
From: Ido Schimmel <idosch@...sch.org>
To: Andrew Lunn <andrew@...n.ch>
Cc: Ido Schimmel <idosch@...lanox.com>, netdev@...r.kernel.org,
linux-kselftest@...r.kernel.org, davem@...emloft.net,
shuah@...nel.org, dsahern@...il.com, nikolay@...ulusnetworks.com,
roopa@...ulusnetworks.com, andy@...yhouse.net, jiri@...lanox.com,
mlxsw@...lanox.com, saeedm@...lanox.com, tariqt@...lanox.com,
jhs@...atatu.com, lucasb@...atatu.com, f.fainelli@...il.com,
vivien.didelot@...oirfairelinux.com, jakub.kicinski@...ronome.com,
simon.horman@...ronome.com
Subject: Re: [RFC PATCH net-next 02/12] selftests: forwarding: Add a test for
FDB learning
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.
Powered by blists - more mailing lists