From: Philipp Herz - Profihost AG <p.herz@profihost.ag>
To: linux-mm@kvack.org
Subject: Vanilla-Kernel 3 - page allocation failure
Date: Tue, 18 Oct 2011 12:24:41 +0200 [thread overview]
Message-ID: <4E9D53E9.9020503@profihost.ag> (raw)
After updating kernel (x86_64) to stable version 3 there are a few
messages appearing in the kernel log such as
kworker/0:1: page allocation failure: order:1, mode:0x20
mysql: page allocation failure: order:1, mode:0x20
php5: page allocation failure: order:1, mode:0x20
Searching the net showed that these messages are known to occur since 2004.
Some people were able to get rid of them by setting
/proc/sys/vm/min_free_kbytes to a high enough value. This does not help
in our case.
Is there a kernel comand line argument to avoid these messages?
As of mm/page_alloc.c these messages are marked to be only warning
messages and would not appear if 'gpf_mask' was set to __GFP_NOWARN in
function warn_alloc_failed.
How does this mask get set? Is it set by the "external" process knocking
at the memory manager?
What is the magic behind the 'order' and 'mode'?
I'm not a subscriber, so please CC me a copy of messages related to the
subject. I'm not sure if I can help much by looking at the inside of the
kernel, but I will try my best to answer any questions concerning this
issue.
Best regards, Philipp
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2011-10-18 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 10:24 Philipp Herz - Profihost AG [this message]
2011-10-19 2:09 ` David Rientjes
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=4E9D53E9.9020503@profihost.ag \
--to=p.herz@profihost.ag \
--cc=linux-mm@kvack.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