linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Barry Song <song.bao.hua@hisilicon.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, linuxarm@huawei.com,
	Mike Kravetz <mike.kravetz@oracle.com>,
	Jonathan Cameron <jonathan.cameron@huawei.com>,
	Roman Gushchin <guro@fb.com>
Subject: Re: [PATCH v3] mm/hugetlb: avoid hardcoding while checking if cma is enable
Date: Tue, 7 Jul 2020 11:18:11 +0300	[thread overview]
Message-ID: <20200707081811.GD9449@kernel.org> (raw)
In-Reply-To: <20200707040204.30132-1-song.bao.hua@hisilicon.com>

On Tue, Jul 07, 2020 at 04:02:04PM +1200, Barry Song wrote:
> hugetlb_cma[0] can be NULL due to various reasons, for example, node0 has
> no memory. so NULL hugetlb_cma[0] doesn't necessarily mean cma is not
> enabled. gigantic pages might have been reserved on other nodes.
> 
> Fixes: cf11e85fc08c ("mm: hugetlb: optionally allocate gigantic hugepages using cma")
> Cc: Mike Kravetz <mike.kravetz@oracle.com>
> Cc: Jonathan Cameron <jonathan.cameron@huawei.com>
> Acked-by: Roman Gushchin <guro@fb.com>
> Signed-off-by: Barry Song <song.bao.hua@hisilicon.com>

Acked-by: Mike Rapoport <rppt@linux.ibm.com>

> ---
>  -v3: add acked-by; make code more canonical 
> 
>  mm/hugetlb.c | 16 +++++++++++++++-
>  1 file changed, 15 insertions(+), 1 deletion(-)
> 
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index 57ece74e3aae..d293c823121e 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -2546,6 +2546,20 @@ static void __init gather_bootmem_prealloc(void)
>  	}
>  }
>  
> +bool __init hugetlb_cma_enabled(void)
> +{
> +#ifdef CONFIG_CMA
> +	int node;
> +
> +	for_each_online_node(node) {
> +		if (hugetlb_cma[node])
> +			return true;
> +	}
> +#endif
> +
> +	return false;
> +}
> +
>  static void __init hugetlb_hstate_alloc_pages(struct hstate *h)
>  {
>  	unsigned long i;
> @@ -2571,7 +2585,7 @@ static void __init hugetlb_hstate_alloc_pages(struct hstate *h)
>  
>  	for (i = 0; i < h->max_huge_pages; ++i) {
>  		if (hstate_is_gigantic(h)) {
> -			if (IS_ENABLED(CONFIG_CMA) && hugetlb_cma[0]) {
> +			if (hugetlb_cma_enabled()) {
>  				pr_warn_once("HugeTLB: hugetlb_cma is enabled, skip boot time allocation\n");
>  				break;
>  			}
> -- 
> 2.27.0
> 
> 
> 

-- 
Sincerely yours,
Mike.


  reply	other threads:[~2020-07-07  8:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-07  4:02 [PATCH v3] mm/hugetlb: avoid hardcoding while checking if cma is enable Barry Song
2020-07-07  8:18 ` Mike Rapoport [this message]
2020-07-07 19:56 ` Andrew Morton
2020-07-08 17:45   ` Mike Kravetz
2020-07-08 18:46     ` Roman Gushchin
2020-07-08 22:11       ` Song Bao Hua (Barry Song)
2020-07-09 18:58         ` Mike Kravetz
2020-07-09 23:45           ` Song Bao Hua (Barry Song)
2020-07-10  0:24             ` Mike Kravetz

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=20200707081811.GD9449@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=guro@fb.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxarm@huawei.com \
    --cc=mike.kravetz@oracle.com \
    --cc=song.bao.hua@hisilicon.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;
as well as URLs for NNTP newsgroup(s).