[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3a82460b-6f58-6e7e-a3d9-141f42069eda@iogearbox.net>
Date: Wed, 13 Apr 2022 16:45:00 +0200
From: Daniel Borkmann <daniel@...earbox.net>
To: Yan Zhu <zhuyan34@...wei.com>, mcgrof@...nel.org
Cc: andrii@...nel.org, ast@...nel.org, bpf@...r.kernel.org,
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, leeyou.li@...wei.com,
laiyuanyuan.lai@...wei.com
Subject: Re: [PATCH v4 sysctl-next] bpf: move bpf sysctls from kernel/sysctl.c
to bpf module
On 4/7/22 9:07 AM, 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 subsystem/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>
Acked-by: Daniel Borkmann <daniel@...earbox.net>
Given the desire is to route this via sysctl-next and we're not shortly
before but after the merge win, could we get a feature branch for bpf-next
to pull from to avoid conflicts with ongoing development cycle?
Thanks,
Daniel
Powered by blists - more mailing lists