netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: David Ahern <dsahern@gmail.com>,
	Ido Schimmel <idosch@mellanox.com>,
	netdev@vger.kernel.org, linux-kselftest@vger.kernel.org
Cc: davem@davemloft.net, shuah@kernel.org,
	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, vivien.didelot@savoirfairelinux.com,
	andrew@lunn.ch, jakub.kicinski@netronome.com,
	simon.horman@netronome.com
Subject: Re: [RFC PATCH net-next 00/12] selftests: forwarding: Add VRF-based tests
Date: Wed, 17 Jan 2018 14:51:04 -0800	[thread overview]
Message-ID: <c8c4a3ef-f21d-0e13-5d35-dfa212c439ab@gmail.com> (raw)
In-Reply-To: <df929bcd-f15e-1897-fc54-c9aba9b65667@gmail.com>

On 01/15/2018 12:14 PM, David Ahern wrote:
> On 1/15/18 12:18 PM, Ido Schimmel wrote:
>> One of the nice things about network namespaces is that they allow one
>> to easily create and test complex environments.
>>
>> Unfortunately, these namespaces can not be used with actual switching
>> ASICs, as their ports can not be migrated to other network namespaces
>> (NETIF_F_NETNS_LOCAL) and most of them probably do not support the
>> L1-separation provided by namespaces.
>>
>> However, a similar kind of flexibility can be achieved by using VRFs and
>> by looping the switch ports together. For example:
>>
>>                              br0
>>                               +
>>                vrf-h1         |           vrf-h2
>>                  +        +---+----+        +
>>                  |        |        |        |
>>     192.0.2.1/24 +        +        +        + 192.0.2.2/24
>>                swp1     swp2     swp3     swp4
>>                  +        +        +        +
>>                  |        |        |        |
>>                  +--------+        +--------+
>>
>> The VRFs act as lightweight namespaces representing hosts connected to
>> the switch.
>>
>> This approach for testing switch ASICs has several advantages over the
>> traditional method that requires multiple physical machines, to name a
>> few:
>>
>> 1. Only the device under test (DUT) is being tested without noise from
>> other system.
>>
>> 2. Ability to easily provision complex topologies. Testing bridging
>> between 4-ports LAGs or 8-way ECMP requires many physical links that are
>> not always available. With the VRF-based approach one merely needs to
>> loopback more ports.
>>
>> These tests are written with switch ASICs in mind, but they can be run
>> on any Linux box using veth pairs to emulate physical loopbacks.
>>
>> Feedback is is welcome. Particularly regarding the best location for
>> these tests (e.g., current location, tools/testing/selftests/net).
>>
> 
> Awesome. Thanks for working on this.

Agreed this is really cool! For DSA enabled switches, we usually have a
host that does the test sequencing and then execute commands remotely on
the DUT, but we might be able to get such a similar framework up and
running on the DUT itself without too much hassle.
-- 
Florian

  parent reply	other threads:[~2018-01-17 22:51 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
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 [this message]
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=c8c4a3ef-f21d-0e13-5d35-dfa212c439ab@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@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).