Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: le berger des photons <thejoff@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] Re: Cake Digest, Vol 131, Issue 2
Date: Thu, 20 Aug 2026 08:56:20 +0200	[thread overview]
Message-ID: <CAO-LeMw+vUsxr6rkUua2Ch_5d9gH13bOofrg4RnpdvQ-iE+NFA@mail.gmail.com> (raw)
In-Reply-To: <178720573798.1010.5425378439583764044@gauss>

what can I read so that your well thought out message can actually make
some sense to me and I could react?

On Thu, Aug 20, 2026 at 8:02 AM <cake-request@lists.bufferbloat.net> wrote:

> Send Cake mailing list submissions to
>         cake@lists.bufferbloat.net
>
> To subscribe or unsubscribe via email, send a message with subject or
> body 'help' to
>         cake-request@lists.bufferbloat.net
>
> You can reach the person managing the list at
>         cake-owner@lists.bufferbloat.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Cake digest..."
>
> Today's Topics:
>
>    1. Re: [PATCH net] net/sched: sch_cake: fix autorate reconfiguration
> throttling
>       (Toke Høiland-Jørgensen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 19 Aug 2026 12:08:52 +0200
> From: Toke Høiland-Jørgensen <toke@toke.dk>
> Subject: [Cake] Re: [PATCH net] net/sched: sch_cake: fix autorate
>         reconfiguration throttling
> To: ooonea <ooonea@gmail.com>
> Cc: Jamal Hadi Salim <jhs@mojatatu.com>, Jiri Pirko
>         <jiri@resnulli.us>, "David S . Miller" <davem@davemloft.net>, Eric
>         Dumazet <edumazet@google.com>, Jakub Kicinski <kuba@kernel.org>,
> Paolo
>         Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
>         cake@lists.bufferbloat.net, netdev@vger.kernel.org,
>         linux-kernel@vger.kernel.org
> Message-ID: <87qzjufmmj.fsf@toke.dk>
> Content-Type: text/plain; charset=utf-8
>
> ooonea <ooonea@gmail.com> writes:
>
> > CAKE's autorate-ingress path intends to limit shaper reconfiguration to
> > once per 250 ms, but last_reconfig_time is only checked and never
> updated.
> > Since the field stays zero, every qualifying capacity-estimate window can
> > call cake_reconfigure(), causing avoidable rate churn and scheduler work
> > under bursty traffic.
> >
> > Store the current timestamp when autorate actually reconfigures the qdisc
> > so the guard enforces the intended interval.
> >
> > Fixes: 7298de9cd725 ("sch_cake: Add ingress mode")
> > Assisted-by: Codex:gpt-5.5
> > Signed-off-by: ooonea <ooonea@gmail.com>
>
> Acked-by: Toke Høiland-Jørgensen <toke@toke.dk>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Cake mailing list -- cake@lists.bufferbloat.net
> To unsubscribe send an email to cake-leave@lists.bufferbloat.net
>
>
> ------------------------------
>
> End of Cake Digest, Vol 131, Issue 2
> ************************************
>

       reply	other threads:[~2026-08-20  6:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <178720573798.1010.5425378439583764044@gauss>
2026-08-20  6:56 ` le berger des photons [this message]
2026-08-20 11:07   ` [Cake] Re: Cake Digest, Vol 131, Issue 2 Frantisek Borsik

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/cake.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=CAO-LeMw+vUsxr6rkUua2Ch_5d9gH13bOofrg4RnpdvQ-iE+NFA@mail.gmail.com \
    --to=thejoff@gmail.com \
    --cc=cake@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