From: Jakub Kicinski <kuba@kernel.org>
To: chia-yu.chang@nokia-bell-labs.com
Cc: netdev@vger.kernel.org, dave.taht@gmail.com, pabeni@redhat.com,
jhs@mojatatu.com, stephen@networkplumber.org,
xiyou.wangcong@gmail.com, jiri@resnulli.us, davem@davemloft.net,
edumazet@google.com, horms@kernel.org, andrew+netdev@lunn.ch,
ij@kernel.org, ncardwell@google.com,
koen.de_schepper@nokia-bell-labs.com, g.white@cablelabs.com,
ingemar.s.johansson@ericsson.com, mirja.kuehlewind@ericsson.com,
cheshire@apple.com, rs.ietf@gmx.at, Jason_Livingood@comcast.com,
vidhi_goel@apple.com, Olga Albisser <olga@albisser.org>,
Olivier Tilmans <olivier.tilmans@nokia.com>,
Henrik Steen <henrist@henrist.net>,
Bob Briscoe <research@bobbriscoe.net>,
Pedro Tammela <pctammela@mojatatu.com>
Subject: Re: [PATCH v5 net-next 1/1] sched: Add dualpi2 qdisc
Date: Mon, 24 Feb 2025 12:30:34 -0800 [thread overview]
Message-ID: <20250224123034.675e0446@kernel.org> (raw)
In-Reply-To: <20250222100725.27838-2-chia-yu.chang@nokia-bell-labs.com>
On Sat, 22 Feb 2025 11:07:25 +0100 chia-yu.chang@nokia-bell-labs.com
wrote:
> From: Koen De Schepper <koen.de_schepper@nokia-bell-labs.com>
>
> DualPI2 provides L4S-type low latency & loss to traffic that uses a
> scalable congestion controller (e.g. TCP-Prague, DCTCP) without
> degrading the performance of 'classic' traffic (e.g. Reno,
> Cubic etc.). It is intended to be the reference implementation of the
> IETF's DualQ Coupled AQM.
Pedro reports that you're missing:
diff --git a/tools/testing/selftests/tc-testing/tdc.sh
b/tools/testing/selftests/tc-testing/tdc.sh
index cddff1772..e64e8acb7 100755
--- a/tools/testing/selftests/tc-testing/tdc.sh
+++ b/tools/testing/selftests/tc-testing/tdc.sh
@@ -63,4 +63,5 @@ try_modprobe sch_hfsc
try_modprobe sch_hhf
try_modprobe sch_htb
try_modprobe sch_teql
+try_modprobe sch_dualpi2
./tdc.py -J`nproc`
--
pw-bot: cr
next prev parent reply other threads:[~2025-02-24 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-22 10:07 [PATCH v5 net-next 0/1] DUALPI2 patch chia-yu.chang
2025-02-22 10:07 ` [PATCH v5 net-next 1/1] sched: Add dualpi2 qdisc chia-yu.chang
2025-02-24 20:30 ` Jakub Kicinski [this message]
2025-02-25 18:07 ` Chia-Yu Chang (Nokia)
2025-02-26 0:41 ` Cong Wang
2025-03-02 15:37 ` Chia-Yu Chang (Nokia)
[not found] ` <s6XvSuJ8nXItuCMN4KLwbJvYh8P3pAtM4TpVWLomsju1tts9T7CGMmmuWSJcIhkC-aXOZndLLoB8jIfDCwdkVH6POUi86FIO5jfkcUhI2nw=@ealdwulf.org.uk>
2025-03-03 1:10 ` Chia-Yu Chang (Nokia)
2025-03-03 16:20 ` Koen De Schepper (Nokia)
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=20250224123034.675e0446@kernel.org \
--to=kuba@kernel.org \
--cc=Jason_Livingood@comcast.com \
--cc=andrew+netdev@lunn.ch \
--cc=cheshire@apple.com \
--cc=chia-yu.chang@nokia-bell-labs.com \
--cc=dave.taht@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=g.white@cablelabs.com \
--cc=henrist@henrist.net \
--cc=horms@kernel.org \
--cc=ij@kernel.org \
--cc=ingemar.s.johansson@ericsson.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=koen.de_schepper@nokia-bell-labs.com \
--cc=mirja.kuehlewind@ericsson.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=olga@albisser.org \
--cc=olivier.tilmans@nokia.com \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=research@bobbriscoe.net \
--cc=rs.ietf@gmx.at \
--cc=stephen@networkplumber.org \
--cc=vidhi_goel@apple.com \
--cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).