Linux MM tree latest commits
 help / color / mirror / Atom feed
From: Roman Gushchin <guro@fb.com>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: <akpm@linux-foundation.org>, <mm-commits@vger.kernel.org>,
	<chenwandun@huawei.com>
Subject: Re: + mm-hugetlb-suppress-wrong-warning-info-when-alloc-gigantic-page.patch added to -mm tree
Date: Fri, 19 Feb 2021 12:11:36 -0800	[thread overview]
Message-ID: <YDAbeDsG7GhV6s6B@carbon.dhcp.thefacebook.com> (raw)
In-Reply-To: <c6a1e494-ae82-5a71-d799-34f0857ecb7c@oracle.com>

On Fri, Feb 19, 2021 at 12:04:32PM -0800, Mike Kravetz wrote:
> On 2/19/21 11:47 AM, Roman Gushchin wrote:
> > On Fri, Feb 19, 2021 at 10:37:17AM -0800, Andrew Morton wrote:
> >>
> >> The patch titled
> >>      Subject: mm/hugetlb: suppress wrong warning info when alloc gigantic page
> >> has been added to the -mm tree.  Its filename is
> >>      mm-hugetlb-suppress-wrong-warning-info-when-alloc-gigantic-page.patch
> >>
> >> This patch should soon appear at
> >>     https://ozlabs.org/~akpm/mmots/broken-out/mm-hugetlb-suppress-wrong-warning-info-when-alloc-gigantic-page.patch  
> >> and later at
> >>     https://ozlabs.org/~akpm/mmotm/broken-out/mm-hugetlb-suppress-wrong-warning-info-when-alloc-gigantic-page.patch  
> >>
> >> Before you just go and hit "reply", please:
> >>    a) Consider who else should be cc'ed
> >>    b) Prefer to cc a suitable mailing list as well
> >>    c) Ideally: find the original patch on the mailing list and do a
> >>       reply-to-all to that, adding suitable additional cc's
> >>
> >> *** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
> >>
> >> The -mm tree is included into linux-next and is updated
> >> there every 3-4 working days
> >>
> >> ------------------------------------------------------
> >> From: Chen Wandun <chenwandun@huawei.com>
> >> Subject: mm/hugetlb: suppress wrong warning info when alloc gigantic page
> >>
> >> If hugetlb_cma is enabled, it will skip boot time allocation when
> >> allocating gigantic page, that doesn't means allocation failure, so
> >> suppress this warning info.
> >>
> >> Link: https://lkml.kernel.org/r/20210219123909.13130-1-chenwandun@huawei.com
> >> Fixes: cf11e85fc08c ("mm: hugetlb: optionally allocate gigantic hugepages using cma")
> >> Signed-off-by: Chen Wandun <chenwandun@huawei.com>
> >> Cc: Roman Gushchin <guro@fb.com>
> >> Cc: Mike Kravetz <mike.kravetz@oracle.com>
> >> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > 
> > Acked-by: Roman Gushchin <guro@fb.com>
> > 
> > Thank!s
> 
> 
> Roman, I was under the impression that this warning provided some value?
> 
> It will only be logged if user asks for both preallocation and cma reservation
> on the command line.  In this case, we ignore the parameter requesting
> preallocation.  It seems reasonable that we log a warning if dropping a
> user requested parameter.

There are two warnings:
"HugeTLB: hugetlb_cma is enabled, skip boot time allocation\n" and
"HugeTLB: allocating %lu of page size %s failed.  Only allocated %lu hugepages.\n"

The point of this patch is to skip printing the second one if the first one is printed.
It makes sense to me.

Thanks!

  reply	other threads:[~2021-02-19 20:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 18:37 + mm-hugetlb-suppress-wrong-warning-info-when-alloc-gigantic-page.patch added to -mm tree akpm
2021-02-19 19:47 ` Roman Gushchin
2021-02-19 20:04   ` Mike Kravetz
2021-02-19 20:11     ` Roman Gushchin [this message]
2021-02-19 21:19       ` Mike Kravetz
  -- strict thread matches above, loose matches on Subject: below --
2021-02-19 23:19 akpm

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=YDAbeDsG7GhV6s6B@carbon.dhcp.thefacebook.com \
    --to=guro@fb.com \
    --cc=akpm@linux-foundation.org \
    --cc=chenwandun@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.kravetz@oracle.com \
    --cc=mm-commits@vger.kernel.org \
    /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