Netdev List
 help / color / mirror / Atom feed
From: Nir Dotan <nird@mellanox.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, mlxsw@mellanox.com, Nir Dotan <nird@mellanox.com>
Subject: [PATCH net-next] selftests: forwarding: gre_multipath: Update next-hop statistics match criteria
Date: Tue,  7 Aug 2018 19:41:55 +0300	[thread overview]
Message-ID: <20180807164155.2831-1-nird@mellanox.com> (raw)

gre_multipath test was using egress vlan_id matching on flows, for the
purpose of collecting next-hops statistics, later to be compared
against configured weights.
As matching on vlan_id on egress direction is not supported on all HW
devices, change the match criteria to use destination IP.

Signed-off-by: Nir Dotan <nird@mellanox.com>
Acked-by: Petr Machata <petrm@mellanox.com>
---
 tools/testing/selftests/net/forwarding/gre_multipath.sh | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/tools/testing/selftests/net/forwarding/gre_multipath.sh b/tools/testing/selftests/net/forwarding/gre_multipath.sh
index 3b1e047..cca2baa 100755
--- a/tools/testing/selftests/net/forwarding/gre_multipath.sh
+++ b/tools/testing/selftests/net/forwarding/gre_multipath.sh
@@ -95,10 +95,10 @@ sw1_create()
 	   nexthop dev g1b
 
 	tc qdisc add dev $ul1 clsact
-	tc filter add dev $ul1 egress pref 111 prot 802.1q \
-	   flower vlan_id 111 action pass
-	tc filter add dev $ul1 egress pref 222 prot 802.1q \
-	   flower vlan_id 222 action pass
+	tc filter add dev $ul1 egress pref 111 prot ipv4 \
+	   flower dst_ip 192.0.2.66 action pass
+	tc filter add dev $ul1 egress pref 222 prot ipv4 \
+	   flower dst_ip 192.0.2.82 action pass
 }
 
 sw1_destroy()
-- 
2.8.4

             reply	other threads:[~2018-08-07 18:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-07 16:41 Nir Dotan [this message]
2018-08-07 23:02 ` [PATCH net-next] selftests: forwarding: gre_multipath: Update next-hop statistics match criteria 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=20180807164155.2831-1-nird@mellanox.com \
    --to=nird@mellanox.com \
    --cc=davem@davemloft.net \
    --cc=mlxsw@mellanox.com \
    --cc=netdev@vger.kernel.org \
    /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