[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49f2c8df-0578-b99e-8687-d77047bd5a33@huawei.com>
Date: Thu, 9 Mar 2023 14:03:39 +0800
From: Kefeng Wang <wangkefeng.wang@...wei.com>
To: HORIGUCHI NAOYA(堀口 直也)
<naoya.horiguchi@....com>
CC: Luis Chamberlain <mcgrof@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Miaohe Lin <linmiaohe@...wei.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
Kees Cook <keescook@...omium.org>,
Iurii Zaikin <yzaikin@...gle.com>
Subject: Re: [PATCH] mm: memory-failure: Move memory failure sysctls to its
own file
On 2023/3/9 13:14, HORIGUCHI NAOYA(堀口 直也) wrote:
> On Thu, Mar 09, 2023 at 12:59:24PM +0800, Kefeng Wang wrote:
>> The sysctl_memory_failure_early_kill and memory_failure_recovery
>> are only used in memory-failure.c, move them to its own file.
>
> Thank you for the patch.
>
> Could you explain the benefit to move them?
> We seem to have many other parameters in kernel/sysctl.c which are used
> only in single places, so why do we handle these two differently?
>
Actually, all of them need to be moved into theirs own file as required
by proc sysctl maintainer, see [1]
> Thanks,
> Naoya Horiguchi
[1] https://lore.kernel.org/all/20211123202347.818157-1-mcgrof@kernel.org/
Powered by blists - more mailing lists