[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251128184852.7ceb3e72@kernel.org>
Date: Fri, 28 Nov 2025 18:48:52 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Toke Høiland-Jørgensen <toke@...e.dk>
Cc: Cong Wang <xiyou.wangcong@...il.com>, Jamal Hadi Salim
<jhs@...atatu.com>, Jiri Pirko <jiri@...nulli.us>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
<pabeni@...hat.com>, Simon Horman <horms@...nel.org>, Jonas
Köppeler <j.koeppeler@...berlin.de>,
cake@...ts.bufferbloat.net, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2 0/4] Multi-queue aware sch_cake
On Fri, 28 Nov 2025 23:33:26 +0100 Toke Høiland-Jørgensen wrote:
> Jakub Kicinski <kuba@...nel.org> writes:
> > On Thu, 27 Nov 2025 20:27:49 +0100 Toke Høiland-Jørgensen wrote:
> >> Yeah; how about I follow up with a selftest after this has been merged
> >> into both the kernel and iproute2?
> >
> > Why is iproute2 a blocker? Because you're not sure if the "API" won't
> > change or because you're worried about NIPA or.. ?
>
> No, just that the patch that adds the new qdisc to iproute2 needs to be
> merged before the selftests can use them. Which they won't be until the
> kernel patches are merged, so we'll have to follow up with the selftests
> once that has happened. IIUC, at least :)
You can add a URL to the branch with the pending iproute2 changes
when you post the selftests and we'll pull them in NIPA, or post
the patches at the same time (just not in one thread).
Powered by blists - more mailing lists