[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220223095019.80080-1-zhuyan34@huawei.com>
Date: Wed, 23 Feb 2022 17:50:19 +0800
From: Yan Zhu <zhuyan34@...wei.com>
To: <alexei.starovoitov@...il.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>, <mcgrof@...nel.org>,
<netdev@...r.kernel.org>, <nixiaoming@...wei.com>,
<songliubraving@...com>, <xiechengliang1@...wei.com>, <yhs@...com>,
<yzaikin@...gle.com>, <zengweilin@...wei.com>,
<zhuyan34@...wei.com>
Subject: Re: [PATCH] bpf: move the bpf syscall sysctl table to its own module
On Tue, Feb 22, 2022 at 9:06 PM Alexei Starovoitov wrote:
> On Tue, Feb 22, 2022 at 5:35 PM Yan Zhu <zhuyan34@...wei.com> wrote:
> >
> > Sysctl table is easier to read under its own module.
>
> "own module"?
> What are you talking about?
I'm sorry I didn't express it clearly. The meaning here is that
the code of bpf syscall sysctl is moved to the bpf module
I will fix it in v2 patch.
> It's not "easier to read" and looks like a pointless churn.
Powered by blists - more mailing lists