[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230310084750.482e633e@hermes.local>
Date: Fri, 10 Mar 2023 08:47:50 -0800
From: Stephen Hemminger <stephen@...workplumber.org>
To: Kui-Feng Lee <kuifeng@...a.com>
Cc: <bpf@...r.kernel.org>, <ast@...nel.org>, <martin.lau@...ux.dev>,
<song@...nel.org>, <kernel-team@...a.com>, <andrii@...nel.org>,
<sdf@...gle.com>, <netdev@...r.kernel.org>
Subject: Re: [PATCH bpf-next v6 2/8] net: Update an existing TCP congestion
control algorithm.
On Thu, 9 Mar 2023 20:38:07 -0800
Kui-Feng Lee <kuifeng@...a.com> wrote:
> This feature lets you immediately transition to another congestion
> control algorithm or implementation with the same name. Once a name
> is updated, new connections will apply this new algorithm.
>
> Signed-off-by: Kui-Feng Lee <kuifeng@...a.com>
What is the use case and userspace API for this?
The congestion control algorithm normally doesn't allow this because
algorithm specific variables (current state of connection) may not
work with another algorithm.
Seems like you are opening Pandora's box here.
Powered by blists - more mailing lists