From: Vladimir Oltean <olteanv@gmail.com>
To: Tobias Waldekranz <tobias@waldekranz.com>
Cc: davem@davemloft.net, kuba@kernel.org, andrew@lunn.ch,
f.fainelli@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH v4 net-next 8/8] selftests: forwarding: ethtool_rmon: Add histogram counter test
Date: Thu, 14 Dec 2023 16:12:18 +0200 [thread overview]
Message-ID: <20231214141218.2qz7onhdp72itxam@skbuf> (raw)
In-Reply-To: <20231214135029.383595-9-tobias@waldekranz.com> <20231214135029.383595-9-tobias@waldekranz.com>
On Thu, Dec 14, 2023 at 02:50:29PM +0100, Tobias Waldekranz wrote:
> Validate the operation of rx and tx histogram counters, if supported
> by the interface, by sending batches of packets targeted for each
> bucket.
>
> Signed-off-by: Tobias Waldekranz <tobias@waldekranz.com>
> ---
Tested-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
# enetc + ocelot
./ethtool_rmon.sh eno0 swp0
TEST: rx-pkts64to64 on eno0 [ OK ]
TEST: rx-pkts65to127 on eno0 [ OK ]
TEST: rx-pkts128to255 on eno0 [ OK ]
TEST: rx-pkts256to511 on eno0 [ OK ]
TEST: rx-pkts512to1023 on eno0 [ OK ]
TEST: rx-pkts1024to1522 on eno0 [ OK ]
TEST: rx-pkts1523to9600 on eno0 [ OK ]
TEST: rx-pkts64to64 on swp0 [ OK ]
TEST: rx-pkts65to127 on swp0 [ OK ]
TEST: rx-pkts128to255 on swp0 [ OK ]
TEST: rx-pkts256to511 on swp0 [ OK ]
TEST: rx-pkts512to1023 on swp0 [ OK ]
TEST: rx-pkts1024to1526 on swp0 [ OK ]
TEST: rx-pkts1527to65535 on swp0 [ OK ]
TEST: tx-pkts64to64 on eno0 [ OK ]
TEST: tx-pkts65to127 on eno0 [ OK ]
TEST: tx-pkts128to255 on eno0 [ OK ]
TEST: tx-pkts256to511 on eno0 [ OK ]
TEST: tx-pkts512to1023 on eno0 [ OK ]
TEST: tx-pkts1024to1522 on eno0 [ OK ]
TEST: tx-pkts1523to9600 on eno0 [ OK ]
TEST: tx-pkts64to64 on swp0 [ OK ]
TEST: tx-pkts65to127 on swp0 [ OK ]
TEST: tx-pkts128to255 on swp0 [ OK ]
TEST: tx-pkts256to511 on swp0 [ OK ]
TEST: tx-pkts512to1023 on swp0 [ OK ]
TEST: tx-pkts1024to1526 on swp0 [ OK ]
TEST: tx-pkts1527to65535 on swp0 [ OK ]
# mv88e6xxx
./ethtool_rmon.sh lan1 lan2
TEST: rx-pkts64to64 on lan1 [ OK ]
TEST: rx-pkts65to127 on lan1 [ OK ]
TEST: rx-pkts128to255 on lan1 [ OK ]
TEST: rx-pkts256to511 on lan1 [ OK ]
TEST: rx-pkts512to1023 on lan1 [ OK ]
TEST: rx-pkts1024to65535 on lan1 [ OK ]
TEST: rx-pkts64to64 on lan2 [ OK ]
TEST: rx-pkts65to127 on lan2 [ OK ]
TEST: rx-pkts128to255 on lan2 [ OK ]
TEST: rx-pkts256to511 on lan2 [ OK ]
TEST: rx-pkts512to1023 on lan2 [ OK ]
TEST: rx-pkts1024to65535 on lan2 [ OK ]
TEST: lan1 does not support tx histogram counters [SKIP]
TEST: lan2 does not support tx histogram counters [SKIP]
This is just lovely, thanks for the work, Tobias.
Just one nitpick below.
> +rmon_histogram()
> +{
> + local iface=$1; shift
> + local neigh=$1; shift
> + local set=$1; shift
> + local nbuckets=0
> + local step=
> +
> + RET=0
> +
> + while read -r -a bucket; do
> + step="$set-pkts${bucket[0]}to${bucket[1]} on $iface"
> +
> + for if in $iface $neigh; do
My syntax highlighting in vim gets confused by the fact that you name a
variable "if". I guess something like "netif" would do the trick. But
bash doesn't seem to be confused. I can send a patch renaming this after
it gets merged. There's no reason to resend - it's not a functional
change.
> + if ! ensure_mtu $if ${bucket[0]}; then
> + log_test_skip "$if does not support the required MTU for $step"
> + return
> + fi
> + done
> +
> + if ! bucket_test $iface $neigh $set $nbuckets ${bucket[0]}; then
> + check_err 1 "$step failed"
> + return 1
> + fi
> + log_test "$step"
> + nbuckets=$((nbuckets + 1))
> + done < <(ethtool --json -S $iface --groups rmon | \
> + jq -r ".[0].rmon[\"${set}-pktsNtoM\"][]|[.low, .high]|@tsv" 2>/dev/null)
next prev parent reply other threads:[~2023-12-14 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 13:50 [PATCH v4 net-next 0/8] net: dsa: mv88e6xxx: Add "eth-mac" and "rmon" counter group support Tobias Waldekranz
2023-12-14 13:50 ` [PATCH v4 net-next 1/8] net: dsa: mv88e6xxx: Push locking into stats snapshotting Tobias Waldekranz
2023-12-14 13:50 ` [PATCH v4 net-next 2/8] net: dsa: mv88e6xxx: Create API to read a single stat counter Tobias Waldekranz
2023-12-14 13:50 ` [PATCH v4 net-next 3/8] net: dsa: mv88e6xxx: Fix mv88e6352_serdes_get_stats error path Tobias Waldekranz
2023-12-14 13:50 ` [PATCH v4 net-next 4/8] net: dsa: mv88e6xxx: Give each hw stat an ID Tobias Waldekranz
2023-12-14 13:50 ` [PATCH v4 net-next 5/8] net: dsa: mv88e6xxx: Add "eth-mac" counter group support Tobias Waldekranz
2023-12-14 13:50 ` [PATCH v4 net-next 6/8] net: dsa: mv88e6xxx: Limit histogram counters to ingress traffic Tobias Waldekranz
2023-12-14 13:50 ` [PATCH v4 net-next 7/8] net: dsa: mv88e6xxx: Add "rmon" counter group support Tobias Waldekranz
2023-12-14 13:50 ` [PATCH v4 net-next 8/8] selftests: forwarding: ethtool_rmon: Add histogram counter test Tobias Waldekranz
2023-12-14 14:12 ` Vladimir Oltean [this message]
2023-12-15 11:10 ` [PATCH v4 net-next 0/8] net: dsa: mv88e6xxx: Add "eth-mac" and "rmon" counter group support patchwork-bot+netdevbpf
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=20231214141218.2qz7onhdp72itxam@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tobias@waldekranz.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