From: Mel Gorman <mel@csn.ul.ie>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Linux Memory Management List <linux-mm@kvack.org>,
Heinz Diehl <htd@fancy-poultry.org>,
David Miller <davem@davemloft.net>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH 2/3] profile: Suppress warning about large allocations when profile=1 is specified
Date: Thu, 16 Jul 2009 11:37:19 +0100 [thread overview]
Message-ID: <20090716103719.GA22499@csn.ul.ie> (raw)
In-Reply-To: <20090716100305.9D16.A69D9226@jp.fujitsu.com>
On Thu, Jul 16, 2009 at 10:12:20AM +0900, KOSAKI Motohiro wrote:
> > When profile= is used, a large buffer is allocated early at boot. This
> > can be larger than what the page allocator can provide so it prints a
> > warning. However, the caller is able to handle the situation so this patch
> > suppresses the warning.
>
> I'm confused.
>
> Currently caller doesn't handle error return.
>
> ----------------------------------------------------------
> asmlinkage void __init start_kernel(void)
> {
> (snip)
> init_timers();
> hrtimers_init();
> softirq_init();
> timekeeping_init();
> time_init();
> sched_clock_init();
> profile_init(); <-- ignore return value
> ------------------------------------------------------------
>
> and, if user want to use linus profiler, the user should choice select
> proper bucket size by boot parameter.
> Currently, allocation failure message tell user about specified bucket size
> is wrong.
> I think this patch hide it.
>
Look at what profile_init() itself is doing. You can't see it from the
patch context but when alloc_pages_exact() fails, it calls vmalloc(). If
that fails, profiling is just disabled. There isn't really anything the
caller of profile_init() can do about it and the page allocator doesn't
need to scream about it.
>
> >
> > Signed-off-by: Mel Gorman <mel@csn.ul.ie>
> > ---
> > kernel/profile.c | 5 +++--
> > 1 files changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/kernel/profile.c b/kernel/profile.c
> > index 69911b5..419250e 100644
> > --- a/kernel/profile.c
> > +++ b/kernel/profile.c
> > @@ -117,11 +117,12 @@ int __ref profile_init(void)
> >
> > cpumask_copy(prof_cpu_mask, cpu_possible_mask);
> >
> > - prof_buffer = kzalloc(buffer_bytes, GFP_KERNEL);
> > + prof_buffer = kzalloc(buffer_bytes, GFP_KERNEL|__GFP_NOWARN);
> > if (prof_buffer)
> > return 0;
> >
> > - prof_buffer = alloc_pages_exact(buffer_bytes, GFP_KERNEL|__GFP_ZERO);
> > + prof_buffer = alloc_pages_exact(buffer_bytes,
> > + GFP_KERNEL|__GFP_ZERO|__GFP_NOWARN);
> > if (prof_buffer)
> > return 0;
>
>
>
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
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:[~2009-07-16 10:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 11:23 [PATCH 0/3] Suppress page allocator warnings about order >= MAX_ORDER (resend) Mel Gorman
2009-07-15 11:23 ` [PATCH 1/3] page-allocator: Allow too high-order warning messages to be suppressed with __GFP_NOWARN Mel Gorman
2009-07-15 19:55 ` David Rientjes
2009-07-16 1:02 ` KOSAKI Motohiro
2009-07-15 11:23 ` [PATCH 2/3] profile: Suppress warning about large allocations when profile=1 is specified Mel Gorman
2009-07-16 1:12 ` KOSAKI Motohiro
2009-07-16 10:37 ` Mel Gorman [this message]
2009-07-16 23:43 ` KOSAKI Motohiro
2009-07-18 10:57 ` [tip:tracing/urgent] " tip-bot for Mel Gorman
2009-07-15 11:23 ` [PATCH 3/3] net-dccp: Suppress warning about large allocations from DCCP Mel Gorman
2009-07-15 13:56 ` Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2009-06-22 15:43 [PATCH 0/3] Suppress page allocator warnings about order >= MAX_ORDER Mel Gorman
2009-06-22 15:43 ` [PATCH 2/3] profile: Suppress warning about large allocations when profile=1 is specified Mel Gorman
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=20090716103719.GA22499@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=htd@fancy-poultry.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
/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).