From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DEBUG_PAGEALLOC & SMP?
Date: Thu, 23 Jun 2005 13:13:06 +0200 [thread overview]
Message-ID: <20050623111306.GA6480@elte.hu> (raw)
In-Reply-To: <20050623094008.GA31207@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> > full log attached below. (ob'fun: the oom-killer picked the migration
> > thread to kill ;)
>
> this was with the -RT tree - let me try whether the same happens on
> vanilla 2.6.12 too.
[ 1 hour later ... ] the mystery is solved: i had a ~15 MB kernel image
size due to various debugging options plus per-CPU tracing buffer at
NR_CPUS=8. PAGEALLOC caused an extra +1MB of DMA-zone kernel footprint
(the 4k granular kernel pagetables of 1 GB physical RAM), which was the
final drop and depleted the DMA pool completely.
Ingo
prev parent reply other threads:[~2005-06-23 11:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 9:09 DEBUG_PAGEALLOC & SMP? Ingo Molnar
2005-06-23 9:20 ` Andrew Morton
2005-06-23 9:29 ` Ingo Molnar
2005-06-23 9:40 ` Ingo Molnar
2005-06-23 11:13 ` Ingo Molnar [this message]
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=20050623111306.GA6480@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--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