From: Jakub Kicinski <kuba@kernel.org>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Paolo Abeni <pabeni@redhat.com>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
syzbot+f63600d288bfb7057424@syzkaller.appspotmail.com,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Simon Horman <horms@kernel.org>,
cake@lists.bufferbloat.net, netdev@vger.kernel.org
Subject: Re: [PATCH net v2] sched: sch_cake: add bounds checks to host bulk flow fairness counts
Date: Thu, 9 Jan 2025 08:18:11 -0800 [thread overview]
Message-ID: <20250109081811.01b7bad1@kernel.org> (raw)
In-Reply-To: <87ikqohswh.fsf@toke.dk>
On Thu, 09 Jan 2025 17:08:14 +0100 Toke Høiland-Jørgensen wrote:
> >> I guess I should have mentioned in the commit message that this was
> >> deliberate. Since it seems you'll be editing that anyway (cf the above),
> >> how about adding a paragraph like:
> >>
> >> As part of this change, the flow quantum calculation is consolidated
> >> into a helper function, which means that the dithering applied to the
> >> host load scaling is now applied both in the DRR rotation and when a
> >> sparse flow's quantum is first initiated. The only user-visible effect
> >> of this is that the maximum packet size that can be sent while a flow
> >> stays sparse will now vary with +/- one byte in some cases. This should
> >> not make a noticeable difference in practice, and thus it's not worth
> >> complicating the code to preserve the old behaviour.
> >
> > It's in Jakub's hands now, possibly he could prefer a repost to reduce
> > the maintainer's overhead.
>
> Alright, sure, I'll respin :)
Hold on, I'll do it :)
next prev parent reply other threads:[~2025-01-09 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 12:01 [PATCH net v2] sched: sch_cake: add bounds checks to host bulk flow fairness counts Toke Høiland-Jørgensen
2025-01-08 16:10 ` [Cake] " Dave Taht
2025-01-09 12:11 ` Paolo Abeni
2025-01-09 12:47 ` Toke Høiland-Jørgensen
2025-01-09 15:06 ` Paolo Abeni
2025-01-09 16:08 ` Toke Høiland-Jørgensen
2025-01-09 16:18 ` Jakub Kicinski [this message]
2025-01-09 16:35 ` Toke Høiland-Jørgensen
2025-01-09 16:30 ` 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=20250109081811.01b7bad1@kernel.org \
--to=kuba@kernel.org \
--cc=cake@lists.bufferbloat.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+f63600d288bfb7057424@syzkaller.appspotmail.com \
--cc=toke@toke.dk \
--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 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.