From: Paul Jackson <pj@sgi.com>
To: Anton Blanchard <anton@samba.org>
Cc: dwalker@mvista.com, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] quieten OOM killer noise
Date: Fri, 8 Jul 2005 22:09:43 -0700 [thread overview]
Message-ID: <20050708220943.1c2e82a5.pj@sgi.com> (raw)
In-Reply-To: <20050703173837.GB15055@krispykreme>
Anton wrote:
> We've had customer situations where that information would have been
> very useful.
I haven't looked closely, but when I provoked the oom killer last week
a few times while working on something else, I did notice that the
printk's that came out were a page or two, per kill. Apparently it
is the arch-specific show_mem() routine that was so verbose - this
was on an ia64 SN2.
Do we really need that lengthy an oom printk? If the other arch's
tend to be a little more terse, then I guess you could catalog my
complaint as a "personal problem" or at least an "arch problem."
In support of this ratelimiting, the other call from main line kernel
code to show_mem(), after the __alloc_pages() message:
page allocation failure. order:%d, mode:0x%x
is already ratelimited. Seems like a good idea.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2005-07-09 5:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 15:02 [PATCH] quieten OOM killer noise Anton Blanchard
2005-07-03 17:26 ` Daniel Walker
2005-07-03 17:38 ` Anton Blanchard
2005-07-03 20:12 ` Daniel Walker
2005-07-04 12:01 ` Al Boldi
2005-07-09 5:09 ` Paul Jackson [this message]
2005-07-05 12:15 ` Thread_Id RVK
2005-07-05 12:55 ` Thread_Id Arjan van de Ven
2005-07-07 12:43 ` Thread_Id Benedikt Spranger
2005-07-14 5:31 ` Thread_Id RVK
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=20050708220943.1c2e82a5.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=dwalker@mvista.com \
--cc=linux-kernel@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