[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yh/V5QN1OhN9IKsI@bombadil.infradead.org>
Date: Wed, 2 Mar 2022 12:39:01 -0800
From: Luis Chamberlain <mcgrof@...nel.org>
To: Yan Zhu <zhuyan34@...wei.com>
Cc: andrii@...nel.org, ast@...nel.org, bpf@...r.kernel.org,
daniel@...earbox.net, john.fastabend@...il.com, kafai@...com,
keescook@...omium.org, kpsingh@...nel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
liucheng32@...wei.com, netdev@...r.kernel.org,
nixiaoming@...wei.com, songliubraving@...com,
xiechengliang1@...wei.com, yhs@...com, yzaikin@...gle.com,
zengweilin@...wei.com
Subject: Re: [PATCH v3 sysctl-next] bpf: move bpf sysctls from
kernel/sysctl.c to bpf module
On Wed, Mar 02, 2022 at 10:04:12AM +0800, Yan Zhu wrote:
> We're moving sysctls out of kernel/sysctl.c as its a mess. We
> already moved all filesystem sysctls out. And with time the goal is
> to move all sysctls out to their own susbsystem/actual user.
>
> kernel/sysctl.c has grown to an insane mess and its easy to run
> into conflicts with it. The effort to move them out is part of this.
>
> Signed-off-by: Yan Zhu <zhuyan34@...wei.com>
Daniel, let me know if this makes more sense now, and if so I can
offer take it through sysctl-next to avoid conflicts more sysctl knobs
get moved out from kernel/sysctl.c.
Luis
Powered by blists - more mailing lists