[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220311071930.GA18301@lst.de>
Date: Fri, 11 Mar 2022 08:19:30 +0100
From: Christoph Hellwig <hch@....de>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Mingbao Sun <sunmingbao@....com>,
Eric Dumazet <edumazet@...gle.com>,
"David S . Miller" <davem@...emloft.net>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
David Ahern <dsahern@...nel.org>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, Christoph Hellwig <hch@....de>,
tyler.sun@...l.com, ping.gan@...l.com, yanxiu.cai@...l.com,
libin.zhang@...l.com, ao.sun@...l.com
Subject: Re: [PATCH] tcp: export symbol tcp_set_congestion_control
On Thu, Mar 10, 2022 at 12:48:25PM -0800, Jakub Kicinski wrote:
> On Thu, 10 Mar 2022 21:48:30 +0800 Mingbao Sun wrote:
> > Since the kernel API 'kernel_setsockopt' was removed, and since the
> > function ‘tcp_set_congestion_control’ is just the real underlying guy
> > handling this job, so it makes sense to get it exported.
>
> Do you happen to have a reference to the commit which removed
> kernel_setsockopt and the justification? My knee jerk reaction
> would the that's a better path than allowing in-kernel socket users
> to poke at internal functions even if that works as of today.
This was part of the set_fs() removal. Back then we decided we'd rather
have type-safe APIs for in-kernel users, which in total was a major
removal of code lines.
Powered by blists - more mailing lists