Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: David Lang <david@lang.hm>, Colin_Higbie <CHigbie1@Higbie.name>
Cc: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: [Starlink] Re: Bufferbloat cure question
Date: Fri, 02 Jan 2026 19:21:56 +0100	[thread overview]
Message-ID: <87o6nbri2j.fsf@toke.dk> (raw)
In-Reply-To: <sosn6297-np2s-4pr0-q2rq-n16n810476n2@ynat.uz>

David Lang via Starlink <starlink@lists.bufferbloat.net> writes:

> Colin_Higbie wrote:
>
>> At 300Mbps or higher, bufferbloat and jitter skyrocket to hundreds of ms, much 
>> worse than not using CAKE at all. I can see one of the 4 router CPU cores 
>> spikes to 100% at those transfer rates whenever I don't limit bandwidth to 
>> something below 280Mbps.
>
> I know I've seen some patches going past in the last couple of months to let 
> cake use more than one CPU, so you may want to look at testing those.

The current version of those patches are here:
https://git.kernel.org/pub/scm/linux/kernel/git/toke/linux.git/log/?h=mq-cake-sub-qdisc

Testing very welcome! I'm planning to resubmit them for upstream
inclusion on Monday :)

-Toke

      reply	other threads:[~2026-01-02 18:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <176388152155.1303.12028700061090443748@gauss>
2025-12-31 22:19 ` [Starlink] Bufferbloat cure question Colin_Higbie
2025-12-31 23:18   ` [Starlink] " Sebastian Moeller
2026-01-01  0:13   ` David Lang
2026-01-02 18:21     ` Toke Høiland-Jørgensen [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

  List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o6nbri2j.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=CHigbie1@Higbie.name \
    --cc=david@lang.hm \
    --cc=starlink@lists.bufferbloat.net \
    /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