public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <hawk@kernel.org>
To: netdev@vger.kernel.org
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	jhs@mojatatu.com, jiri@resnulli.us, j.koeppeler@tu-berlin.de,
	kernel-team@cloudflare.com
Subject: Re: [PATCH net-next 5/5] selftests: net: add veth BQL stress test
Date: Thu, 26 Mar 2026 13:19:18 +0100	[thread overview]
Message-ID: <f1263c70-ef11-4622-93bf-a5f5acaf735c@kernel.org> (raw)
In-Reply-To: <20260324174719.1224337-7-hawk@kernel.org>



On 24/03/2026 18.47, hawk@kernel.org wrote:
> From: Jesper Dangaard Brouer<hawk@kernel.org>
> 
> Add a selftest that exercises veth's BQL (Byte Queue Limits) code path
> under sustained UDP load. The test creates a veth pair with GRO enabled
> (activating the NAPI path and BQL), attaches a qdisc, optionally loads
> iptables rules in the consumer namespace to slow NAPI processing, and
> floods UDP packets for a configurable duration.
> 
[...]
> 
> Signed-off-by: Jesper Dangaard Brouer<hawk@kernel.org>
> Tested-by: Jonas Köppeler<j.koeppeler@tu-berlin.de>
> ---
>   tools/testing/selftests/net/veth_bql_test.sh  | 784 ++++++++++++++++++
>   .../selftests/net/veth_bql_test_virtme.sh     | 124 +++
>   2 files changed, 908 insertions(+)
>   create mode 100755 tools/testing/selftests/net/veth_bql_test.sh
>   create mode 100755 tools/testing/selftests/net/veth_bql_test_virtme.sh
> 
> diff --git a/tools/testing/selftests/net/veth_bql_test.sh b/tools/testing/selftests/net/veth_bql_test.sh
> new file mode 100755
> index 000000000000..9b5923341040
> --- /dev/null
> +++ b/tools/testing/selftests/net/veth_bql_test.sh

The netdev/shellcheck [0][1] had some review comments.
I will work on addressing these.

[0] 
https://netdev-ctrl.bots.linux.dev/logs/build/1071815/14493217/shellcheck/stdout
[1] https://www.shellcheck.net/

pw-bot: changes-requested

--Jesper

  reply	other threads:[~2026-03-26 12:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24 17:46 [PATCH net-next 0/5] veth: add Byte Queue Limits (BQL) support hawk
2026-03-24 17:46 ` [PATCH " hawk
2026-03-24 17:56   ` Jesper Dangaard Brouer
2026-03-24 17:47 ` [PATCH net-next 1/5] net: add dev->bql flag to allow BQL sysfs for IFF_NO_QUEUE devices hawk
2026-03-24 17:47 ` [PATCH net-next 2/5] veth: implement Byte Queue Limits (BQL) for latency reduction hawk
2026-03-24 17:47 ` [PATCH net-next 3/5] veth: add tx_timeout watchdog as BQL safety net hawk
2026-03-24 17:47 ` [PATCH net-next 4/5] net: sched: add timeout count to NETDEV WATCHDOG message hawk
2026-03-24 17:47 ` [PATCH net-next 5/5] selftests: net: add veth BQL stress test hawk
2026-03-26 12:19   ` Jesper Dangaard Brouer [this message]
2026-03-26 19:55     ` Jakub Kicinski

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=f1263c70-ef11-4622-93bf-a5f5acaf735c@kernel.org \
    --to=hawk@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=j.koeppeler@tu-berlin.de \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kernel-team@cloudflare.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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