From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Luis Chamberlain <mcgrof@kernel.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
Muchun Song <muchun.song@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>,
Iurii Zaikin <yzaikin@google.com>
Subject: Re: [PATCH] mm: hugetlb: move hugeltb sysctls to its own file
Date: Fri, 10 Mar 2023 22:23:34 +0800 [thread overview]
Message-ID: <a9375f3c-bd8b-8d32-2fd2-32047005f9b5@huawei.com> (raw)
In-Reply-To: <20230309122011.61969-1-wangkefeng.wang@huawei.com>
On 2023/3/9 20:20, Kefeng Wang wrote:
> This moves all hugetlb sysctls to its own file, also kill an
> useless hugetlb_treat_movable_handler() defination.
>
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> ---
> include/linux/hugetlb.h | 8 -------
> kernel/sysctl.c | 32 --------------------------
> mm/hugetlb.c | 51 ++++++++++++++++++++++++++++++++++++++---
> 3 files changed, 48 insertions(+), 43 deletions(-)
>
> +#ifdef CONFIG_SYSCTL
> +static void hugetlb_sysctl_init(void);
Hi Luis,this should add __init as it is called by hugetlb_init,
could you help to change it, or I could send a new patch.
> +#else
> +static inline void hugetlb_sysctl_init(void) { }
> +#endif
> +
> static int __init hugetlb_init(void)
> {
> int i;
> @@ -4257,6 +4263,7 @@ static int __init hugetlb_init(void)
>
> hugetlb_sysfs_init();
> hugetlb_cgroup_file_init();
> + hugetlb_sysctl_init();
>
...
> +
> +static void hugetlb_sysctl_init(void)
ditto, sorry for the mistake.
Thanks.
> +{
> + register_sysctl_init("vm", hugetlb_table);
> +}
> #endif /* CONFIG_SYSCTL */
>
> void hugetlb_report_meminfo(struct seq_file *m)
next prev parent reply other threads:[~2023-03-10 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 12:20 Kefeng Wang
2023-03-09 20:34 ` Luis Chamberlain
2023-03-09 21:08 ` Andrew Morton
2023-03-09 22:20 ` Luis Chamberlain
2023-03-09 21:30 ` Mike Kravetz
2023-03-10 2:36 ` Muchun Song
2023-03-10 14:23 ` Kefeng Wang [this message]
2023-03-10 19:53 ` Luis Chamberlain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a9375f3c-bd8b-8d32-2fd2-32047005f9b5@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=muchun.song@linux.dev \
--cc=yzaikin@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox