From: Stephen Hemminger <stephen@networkplumber.org>
To: Christophe Burdinat <c.burdinat@ateme.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [BUG] net/sched: netem: delay correlation has no effect
Date: Sun, 4 Oct 2026 10:45:26 -0700 [thread overview]
Message-ID: <20261004104526.56a61ca5@phoenix.local> (raw)
In-Reply-To: <PATP264MB7825D08FBDEB801422FD6EFD93892@PATP264MB7825.FRAP264.PROD.OUTLOOK.COM>
On Fri, 2 Oct 2026 16:50:07 +0000
Christophe Burdinat <c.burdinat@ateme.com> wrote:
> Hello,
>
> Context: we found the following while evaluating a QUIC-based protocol (Media over QUIC) with netem-based network profiles from a 3GPP study (TR 26.934), where the reordering caused by per-packet jitter makes QUIC declare many packets lost and changes the results substantially. The following report has been generated with Claude code, but humanly reviewed.
Thanks for the bug report. Will look into it but do not expect anything soon.
This code is over 20 years old, and it may just be you are trying to use
it in a way that was never intended.
prev parent reply other threads:[~2026-10-04 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 16:50 [BUG] net/sched: netem: delay correlation has no effect Christophe Burdinat
2026-10-04 17:45 ` Stephen Hemminger [this message]
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=20261004104526.56a61ca5@phoenix.local \
--to=stephen@networkplumber.org \
--cc=c.burdinat@ateme.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