All of lore.kernel.org
 help / color / mirror / Atom feed
From: petrm at mellanox.com (Petr Machata)
Subject: [PATCH net-next 0/5] A test for mirror-to-gretap with team in UL packet path
Date: Mon, 30 Jul 2018 16:37:17 +0200	[thread overview]
Message-ID: <cover.1532961216.git.petrm@mellanox.com> (raw)

This patchset adds a test for "tc action mirred mirror" where the
mirrored-to device is a gretap, and underlay path contains a team
device.

In patch #1 require_command() is added, which should henceforth be used
to declare dependence on a certain tool.

In patch #2, two new functions, team_create() and team_destroy(), are
added to lib.sh.

The newly-added test uses arping, which isn't necessarily available.
Therefore patch #3 introduces $ARPING, and a preexisting test is fixed
to require_command $ARPING.

In patches #4 and #5, two new tests are added. In both cases, a team
device is on egress path of a mirrored packet in a mirror-to-gretap
scenario. In the first one, the team device is in loadbalance mode, in
the second one it's in lacp mode. (The difference in modes necessitates
a different testing strategy, hence two test cases instead of just
parameterizing one.)

Petr Machata (5):
  selftests: forwarding: lib: Add require_command()
  selftests: forwarding: lib: Support team devices
  selftests: forwarding: Introduce $ARPING
  selftests: forwarding: Test mirror-to-gretap w/ UL team
  selftests: forwarding: Test mirror-to-gretap w/ UL team LACP

 tools/testing/selftests/net/forwarding/lib.sh      |  43 +++-
 .../net/forwarding/mirror_gre_bridge_1q_lag.sh     | 283 ++++++++++++++++++++
 .../net/forwarding/mirror_gre_lag_lacp.sh          | 285 +++++++++++++++++++++
 .../net/forwarding/mirror_gre_vlan_bridge_1q.sh    |   6 +-
 4 files changed, 607 insertions(+), 10 deletions(-)
 create mode 100755 tools/testing/selftests/net/forwarding/mirror_gre_bridge_1q_lag.sh
 create mode 100755 tools/testing/selftests/net/forwarding/mirror_gre_lag_lacp.sh

-- 
2.4.11

--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: petrm@mellanox.com (Petr Machata)
Subject: [PATCH net-next 0/5] A test for mirror-to-gretap with team in UL packet path
Date: Mon, 30 Jul 2018 16:37:17 +0200	[thread overview]
Message-ID: <cover.1532961216.git.petrm@mellanox.com> (raw)
Message-ID: <20180730143717.t3dxdHDgzgjDh6VOxZvxmYOd7oCBwoRExV-LM9B85MA@z> (raw)

This patchset adds a test for "tc action mirred mirror" where the
mirrored-to device is a gretap, and underlay path contains a team
device.

In patch #1 require_command() is added, which should henceforth be used
to declare dependence on a certain tool.

In patch #2, two new functions, team_create() and team_destroy(), are
added to lib.sh.

The newly-added test uses arping, which isn't necessarily available.
Therefore patch #3 introduces $ARPING, and a preexisting test is fixed
to require_command $ARPING.

In patches #4 and #5, two new tests are added. In both cases, a team
device is on egress path of a mirrored packet in a mirror-to-gretap
scenario. In the first one, the team device is in loadbalance mode, in
the second one it's in lacp mode. (The difference in modes necessitates
a different testing strategy, hence two test cases instead of just
parameterizing one.)

Petr Machata (5):
  selftests: forwarding: lib: Add require_command()
  selftests: forwarding: lib: Support team devices
  selftests: forwarding: Introduce $ARPING
  selftests: forwarding: Test mirror-to-gretap w/ UL team
  selftests: forwarding: Test mirror-to-gretap w/ UL team LACP

 tools/testing/selftests/net/forwarding/lib.sh      |  43 +++-
 .../net/forwarding/mirror_gre_bridge_1q_lag.sh     | 283 ++++++++++++++++++++
 .../net/forwarding/mirror_gre_lag_lacp.sh          | 285 +++++++++++++++++++++
 .../net/forwarding/mirror_gre_vlan_bridge_1q.sh    |   6 +-
 4 files changed, 607 insertions(+), 10 deletions(-)
 create mode 100755 tools/testing/selftests/net/forwarding/mirror_gre_bridge_1q_lag.sh
 create mode 100755 tools/testing/selftests/net/forwarding/mirror_gre_lag_lacp.sh

-- 
2.4.11

--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Petr Machata <petrm@mellanox.com>
To: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org
Cc: davem@davemloft.net, shuah@kernel.org
Subject: [PATCH net-next 0/5] A test for mirror-to-gretap with team in UL packet path
Date: Mon, 30 Jul 2018 16:37:17 +0200	[thread overview]
Message-ID: <cover.1532961216.git.petrm@mellanox.com> (raw)

This patchset adds a test for "tc action mirred mirror" where the
mirrored-to device is a gretap, and underlay path contains a team
device.

In patch #1 require_command() is added, which should henceforth be used
to declare dependence on a certain tool.

In patch #2, two new functions, team_create() and team_destroy(), are
added to lib.sh.

The newly-added test uses arping, which isn't necessarily available.
Therefore patch #3 introduces $ARPING, and a preexisting test is fixed
to require_command $ARPING.

In patches #4 and #5, two new tests are added. In both cases, a team
device is on egress path of a mirrored packet in a mirror-to-gretap
scenario. In the first one, the team device is in loadbalance mode, in
the second one it's in lacp mode. (The difference in modes necessitates
a different testing strategy, hence two test cases instead of just
parameterizing one.)

Petr Machata (5):
  selftests: forwarding: lib: Add require_command()
  selftests: forwarding: lib: Support team devices
  selftests: forwarding: Introduce $ARPING
  selftests: forwarding: Test mirror-to-gretap w/ UL team
  selftests: forwarding: Test mirror-to-gretap w/ UL team LACP

 tools/testing/selftests/net/forwarding/lib.sh      |  43 +++-
 .../net/forwarding/mirror_gre_bridge_1q_lag.sh     | 283 ++++++++++++++++++++
 .../net/forwarding/mirror_gre_lag_lacp.sh          | 285 +++++++++++++++++++++
 .../net/forwarding/mirror_gre_vlan_bridge_1q.sh    |   6 +-
 4 files changed, 607 insertions(+), 10 deletions(-)
 create mode 100755 tools/testing/selftests/net/forwarding/mirror_gre_bridge_1q_lag.sh
 create mode 100755 tools/testing/selftests/net/forwarding/mirror_gre_lag_lacp.sh

-- 
2.4.11

             reply	other threads:[~2018-07-30 14:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30 14:37 petrm [this message]
2018-07-30 14:37 ` [PATCH net-next 0/5] A test for mirror-to-gretap with team in UL packet path Petr Machata
2018-07-30 14:37 ` Petr Machata
2018-07-30 14:39 ` [PATCH net-next 1/5] selftests: forwarding: lib: Add require_command() petrm
2018-07-30 14:39   ` Petr Machata
2018-07-30 14:39   ` Petr Machata
2018-07-30 14:39 ` [PATCH net-next 2/5] selftests: forwarding: lib: Support team devices petrm
2018-07-30 14:39   ` Petr Machata
2018-07-30 14:39   ` Petr Machata
2018-07-30 14:39 ` [PATCH net-next 3/5] selftests: forwarding: Introduce $ARPING petrm
2018-07-30 14:39   ` Petr Machata
2018-07-30 14:39   ` Petr Machata
2018-07-30 14:40 ` [PATCH net-next 4/5] selftests: forwarding: Test mirror-to-gretap w/ UL team petrm
2018-07-30 14:40   ` Petr Machata
2018-07-30 14:40   ` Petr Machata
2018-07-30 14:40 ` [PATCH net-next 5/5] selftests: forwarding: Test mirror-to-gretap w/ UL team LACP petrm
2018-07-30 14:40   ` Petr Machata
2018-07-30 14:40   ` Petr Machata
2018-07-30 16:48 ` [PATCH net-next 0/5] A test for mirror-to-gretap with team in UL packet path davem
2018-07-30 16:48   ` David Miller
2018-07-30 16:48   ` David Miller

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=cover.1532961216.git.petrm@mellanox.com \
    --to=unknown@example.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.