[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230309051439.GA4018963@hori.linux.bs1.fc.nec.co.jp>
Date: Thu, 9 Mar 2023 05:14:41 +0000
From: HORIGUCHI NAOYA(堀口 直也)
<naoya.horiguchi@....com>
To: Kefeng Wang <wangkefeng.wang@...wei.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 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?
Thanks,
Naoya Horiguchi
Powered by blists - more mailing lists