From: Michal Hocko <mhocko@suse.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: sgruszka@redhat.com, akpm@linux-foundation.org,
linux-mm@kvack.org, rjw@sisk.pl, aarcange@redhat.com,
cl@linux-foundation.org, mgorman@suse.de, penberg@cs.helsinki.fi
Subject: Re: [PATCH] mm, page_alloc: Remove debug_guardpage_minorder() test in warn_alloc().
Date: Wed, 12 Apr 2017 14:30:42 +0200 [thread overview]
Message-ID: <20170412123042.GF7157@dhcp22.suse.cz> (raw)
In-Reply-To: <201704122114.JDG73963.SFFLVQOOtMJHFO@I-love.SAKURA.ne.jp>
On Wed 12-04-17 21:14:10, Tetsuo Handa wrote:
> Stanislaw Gruszka wrote:
> > On Wed, Apr 12, 2017 at 01:35:28PM +0200, Michal Hocko wrote:
> > > OK, I see. That is a rather weird feature and the naming is more than
> > > surprising. But put that aside. Then it means that the check should be
> > > pulled out to
> > > diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> > > index 6632256ef170..1e5f3b5cdb87 100644
> > > --- a/mm/page_alloc.c
> > > +++ b/mm/page_alloc.c
> > > @@ -3941,7 +3941,8 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int order,
> > > goto retry;
> > > }
> > > fail:
> > > - warn_alloc(gfp_mask, ac->nodemask,
> > > + if (!debug_guardpage_minorder())
> > > + warn_alloc(gfp_mask, ac->nodemask,
> > > "page allocation failure: order:%u", order);
> > > got_pg:
> > > return page;
> >
> > Looks good to me assuming it will be applied on top of Tetsuo's patch.
> >
> > Reviewed-by: Stanislaw Gruszka <sgruszka@redhat.com>
> >
>
> There are two warn_alloc() usages in mm/vmalloc.c which the check should be
> pulled out.
Do we actually care about vmalloc for this?
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-04-12 12:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 11:27 Tetsuo Handa
2017-04-12 10:23 ` Stanislaw Gruszka
2017-04-12 10:41 ` Tetsuo Handa
2017-04-12 11:08 ` Stanislaw Gruszka
2017-04-12 10:59 ` Michal Hocko
2017-04-12 11:21 ` Stanislaw Gruszka
2017-04-12 11:35 ` Michal Hocko
2017-04-12 11:48 ` Stanislaw Gruszka
2017-04-12 12:12 ` Michal Hocko
2017-04-12 12:14 ` Tetsuo Handa
2017-04-12 12:30 ` Michal Hocko [this message]
2017-04-12 13:49 ` Tetsuo Handa
2017-04-12 14:07 ` Michal Hocko
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=20170412123042.GF7157@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=penberg@cs.helsinki.fi \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=rjw@sisk.pl \
--cc=sgruszka@redhat.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