From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Marco Nietz <m.nietz-mm@iplabs.de>
Cc: balbir@linux.vnet.ibm.com, linux-mm@kvack.org
Subject: Re: oom-killer why ?
Date: Tue, 26 Aug 2008 18:48:41 +0530 [thread overview]
Message-ID: <48B402B1.8030902@linux.vnet.ibm.com> (raw)
In-Reply-To: <48B401F8.9010703@linux.vnet.ibm.com>
Balbir Singh wrote:
> Marco Nietz wrote:
>> Balbir Singh schrieb:
>>
>>>> DMA32 free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB
>>>> present:0kB pages_scanned:0 all_unreclaimable? no
>>>> lowmem_reserve[]: 0 0 880 17392
>>> pages_scanned is 0
>> Is'nt this zone irrelevant for a 32bit Kernel ?
>>
>
> Doesn't matter, since you have 0 present pages.
>
>>>> Normal free:3664kB min:3756kB low:4692kB high:5632kB active:280kB
>>>> inactive:244kB present:901120kB pages_scanned:593 all_unreclaimable? yes
>>>> lowmem_reserve[]: 0 0 0 132096
>>> pages_scanned is 593 and all_unreclaimable is yes
>> Reclaimable means, that the Pages are reusable for other Purposes, or not ?
>>
>
> It is set by a background routine that tries to reclaim pages (balance_pgdat()),
> to indicate that it was unable to reclaim any pages from the zone, even though
> it did a certain amount of work to do so.
>
>>>> HighMem free:5941820kB min:512kB low:18148kB high:35784kB
>>>> active:4408096kB inactive:5494404kB present:16908288kB pages_scanned:0
>>>> all_unreclaimable? no
>>> pages_scanned is 0
>>> Do you have CONFIG_HIGHPTE set? I suspect you don't (I don't really know the
>>> debian etch configuration)
>> No, it's not set in the running Debian Kernel.
>
> Looks like CONFIG_HIGHPTE=y would have helped allocate pages since you do have
> pages in HighMem available.
>
Looking closely, may be there is a leak like Christoph suggested (most of the
pages have been consumed by the kernel) - only 280kB+244kB is in use by user
pages. The rest has either leaked or in use by the kernel.
--
Balbir
--
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:[~2008-08-26 13:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 11:25 oom-killer why ? Marco Nietz
2008-08-25 15:56 ` Christoph Lameter
2008-08-25 16:18 ` Marco Nietz
2008-08-25 16:29 ` Christoph Lameter
2008-08-25 17:26 ` Marco Nietz
2008-08-25 18:55 ` Christoph Lameter
2008-08-26 6:44 ` Marco Nietz
2008-08-26 13:23 ` Christoph Lameter
2008-08-26 10:45 ` Larry Woodman
2008-08-25 17:36 ` Larry Woodman
2008-08-26 11:11 ` Balbir Singh
2008-08-26 12:00 ` Marco Nietz
2008-08-26 13:15 ` Balbir Singh
2008-08-26 13:18 ` Balbir Singh [this message]
2008-08-26 19:09 ` Larry Woodman
2008-08-27 2:32 ` Balbir Singh
2008-08-27 6:21 ` Marco Nietz
2008-08-30 18:19 ` Rik van Riel
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=48B402B1.8030902@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=linux-mm@kvack.org \
--cc=m.nietz-mm@iplabs.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.