From: Muchun Song <muchun.song@linux.dev>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Oscar Salvador <osalvador@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] mm/hugetlb: Make __NR_USED_SUBPAGE check conditional
Date: Tue, 3 Dec 2024 11:29:18 +0800 [thread overview]
Message-ID: <A9973D39-9840-40F2-91DA-1CA8ADC06AA1@linux.dev> (raw)
In-Reply-To: <20241203023207.123416-1-anshuman.khandual@arm.com>
> On Dec 3, 2024, at 10:32, Anshuman Khandual <anshuman.khandual@arm.com> wrote:
>
> The HugeTLB order check against __NR_USED_SUBPAGE is required only when
> HUGETLB_PAGE_OPTIMIZE_VMEMMAP is enabled. Hence BUG_ON() trigger should
> happen only when applicable.
>
> Cc: Muchun Song <muchun.song@linux.dev>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Oscar Salvador <osalvador@suse.de>
> Cc: linux-mm@kvack.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
> ---
> This patch applies on v6.13-rc1
>
> Changes in V2:
>
> - Fixed #ifdef with CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP per Oscar
>
> Changes in V1:
>
> https://lore.kernel.org/all/20241202090728.78935-1-anshuman.khandual@arm.com/
>
> mm/hugetlb.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index ea2ed8e301ef..e6a5b21e3578 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -4513,11 +4513,13 @@ void __init hugetlb_add_hstate(unsigned int order)
> struct hstate *h;
> unsigned long i;
>
> - if (size_to_hstate(PAGE_SIZE << order)) {
> + if (size_to_hstate(PAGE_SIZE << order))
> return;
> - }
> +
> BUG_ON(hugetlb_max_hstate >= HUGE_MAX_HSTATE);
> +#ifdef CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP
> BUG_ON(order < order_base_2(__NR_USED_SUBPAGE));
Hi Anshuman,
__NR_USED_SUBPAGE indicates how many struct pages are used to store
extra metadata for a HugeTLB page. So we need to make sure the order
of a HugeTLB page should be bigger than or equal to order_base_2(__NR_USED_SUBPAGE).
So It is not related to HVO. I don't think the changes make sense.
Thanks.
> +#endif
> h = &hstates[hugetlb_max_hstate++];
> __mutex_init(&h->resize_lock, "resize mutex", &h->resize_key);
> h->order = order;
> --
> 2.30.2
>
next prev parent reply other threads:[~2024-12-03 3:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 2:32 Anshuman Khandual
2024-12-03 3:29 ` Muchun Song [this message]
2024-12-03 7:46 ` Anshuman Khandual
2024-12-03 8:20 ` Muchun Song
2024-12-04 2:46 ` Anshuman Khandual
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=A9973D39-9840-40F2-91DA-1CA8ADC06AA1@linux.dev \
--to=muchun.song@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
/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