All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Vecera <ivecera@redhat.com>
To: netdev@vger.kernel.org
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
	Jiri Pirko <jiri@resnulli.us>, Shuah Khan <shuah@kernel.org>,
	linux-kselftest@vger.kernel.org (open list:KERNEL SELFTEST
	FRAMEWORK), linux-kernel@vger.kernel.org (open list)
Subject: [PATCH net-next] selftests: tc-testing: preload all qdisc modules enabled in config
Date: Wed, 14 Oct 2026 14:20:45 +0200	[thread overview]
Message-ID: <20261014122045.2375722-1-ivecera@redhat.com> (raw)

tdc.sh preloads only some of the qdisc modules that the tc-testing
config enables. Add the missing ones: ingress, mqprio, multiq, netem,
pie, plug, prio, qfq, red, sfb, sfq, skbprio, taprio and tbf.

Signed-off-by: Ivan Vecera <ivecera@redhat.com>
---
 tools/testing/selftests/tc-testing/tdc.sh | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/tools/testing/selftests/tc-testing/tdc.sh b/tools/testing/selftests/tc-testing/tdc.sh
index dae19687912d..25cdc256287d 100755
--- a/tools/testing/selftests/tc-testing/tdc.sh
+++ b/tools/testing/selftests/tc-testing/tdc.sh
@@ -65,6 +65,20 @@ try_modprobe sch_gred
 try_modprobe sch_hfsc
 try_modprobe sch_hhf
 try_modprobe sch_htb
+try_modprobe sch_ingress
+try_modprobe sch_mqprio
+try_modprobe sch_multiq
+try_modprobe sch_netem
+try_modprobe sch_pie
+try_modprobe sch_plug
+try_modprobe sch_prio
+try_modprobe sch_qfq
+try_modprobe sch_red
+try_modprobe sch_sfb
+try_modprobe sch_sfq
+try_modprobe sch_skbprio
+try_modprobe sch_taprio
+try_modprobe sch_tbf
 try_modprobe sch_teql
 try_modprobe sch_dualpi2
 ./tdc.py -J"$(nproc)"
-- 
2.56.0


             reply	other threads:[~2026-10-14 12:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14 12:20 Ivan Vecera [this message]
2026-10-16  2:42 ` [PATCH net-next] selftests: tc-testing: preload all qdisc modules enabled in config Hangbin Liu
2026-10-20 11:10 ` 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=20261014122045.2375722-1-ivecera@redhat.com \
    --to=ivecera@redhat.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shuah@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 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.