From: Matthias Wolle <Matthias.Wolle@gmx.de>
To: Andi Kleen <andi@firstfloor.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: LowFree/LowMem problem
Date: Fri, 25 Jan 2008 02:45:34 +0100 [thread overview]
Message-ID: <200801250245.35013.Matthias.Wolle@gmx.de> (raw)
In-Reply-To: <p73d4rrae1y.fsf@bingen.suse.de>
On Thursday 24 January 2008 08:16 Andi Kleen wrote:
> Do you perhaps have a kernel compiled without CONFIG_HIGHPTE? Normally
> __pte_alloc should be able to allocate highmem unless that option is
> not set. Before HIGHPTE was implemented running out of low memory
> due to page tables was pretty common.
The kernel from 17th Jan 2008 didn't have CONFIG_HIGHPTE enabled. Yesterday we
checked a 2.6.23.14 kernel with CONFIG_HIGHPTE enabled. The 4GB test machine
showed the same fast low memory reducing effect. LowFree stopped at 400MB
like without CONFIG_HIGHPTE. A 2GB machine had a limit of 690MB LowFree. The
difference of LowTotal and LowFree is shown as used memory. In case of the
4GB machine, this means I have 400MB used memory which is not related to any
process.
I hope this helps. I can't test on the 16GB RAM machines anymore, because they
are working productive now.
> BTW the ultimate fix for most lowmem problems is to go 64bit
We switched back to the distribution default 2.6.18-bigmem kernel of debian
which doesn't have this problem. On this kernel the test script has no effect
to the low memory.
Regards
Matthias
On Thursday 24 January 2008 08:16 Andi Kleen wrote:
> Matthias Wolle <Matthias.Wolle@gmx.de> writes:
> > Jan 17 23:31:58 franklin72 kernel: sshd invoked oom-killer:
> > gfp_mask=0xd0, order=0, oomkilladj=0 Jan 17 23:31:58 franklin72 kernel:
> > cat invoked oom-killer: gfp_mask=0x84d0, order=0, oomkilladj=0 Jan 17
> > 23:31:58 franklin72 kernel: [<c014af39>] out_of_memory+0x69/0x1a4 Jan 17
> > 23:31:58 franklin72 kernel: [<c014c588>] __alloc_pages+0x20a/0x291 Jan
> > 17 23:31:58 franklin72 kernel: [<c0153618>] __pte_alloc+0x11/0x94
>
> Do you perhaps have a kernel compiled without CONFIG_HIGHPTE? Normally
> __pte_alloc should be able to allocate highmem unless that option is
> not set. Before HIGHPTE was implemented running out of low memory
> due to page tables was pretty common.
>
> BTW the ultimate fix for most lowmem problems is to go 64bit
>
> -Andi
next prev parent reply other threads:[~2008-01-25 1:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 5:32 Matthias Wolle
2008-01-23 22:06 ` Andrew Morton
2008-01-23 22:40 ` Matthias Wolle
2008-01-24 7:16 ` Andi Kleen
2008-01-25 1:45 ` Matthias Wolle [this message]
2008-01-21 16:45 Parag Warudkar
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=200801250245.35013.Matthias.Wolle@gmx.de \
--to=matthias.wolle@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.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
Powered by JetHome