linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@gmail.com>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Minchan Kim <minchan.kim@gmail.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Kernel Testers List <kernel-testers@vger.kernel.org>,
	David Howells <dhowells@redhat.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Subject: Re: OOM killer in 2.6.31-rc2
Date: Wed, 8 Jul 2009 13:15:15 +0800	[thread overview]
Message-ID: <20090708051515.GA17156@localhost> (raw)
In-Reply-To: <200907072342.07822.gene.heskett@verizon.net>

On Tue, Jul 07, 2009 at 11:42:07PM -0400, Gene Heskett wrote:
> On Tuesday 07 July 2009, Wu Fengguang wrote:
> >On Tue, Jul 07, 2009 at 10:57:30PM +0800, Gene Heskett wrote:
> >> On Tuesday 07 July 2009, Wu Fengguang wrote:
> >> >On Mon, Jul 06, 2009 at 10:56:00AM -0400, Gene Heskett wrote:
> >> >> Greetings all;
> [...]
> >> >
> >> >Normal zone is absent in the above lines.
> >>
> >> Is this a .config issue?
> >
> >At least CONFIG_HIGHMEM64G is not necessary, could try disabling it.
> 
> I have in a rebuild of this 2.6.30.1 kernel, but ISTR I enabled that because 
> it was only using 3G of the 4G of ram in this box, an AMD-64 Phenom, 4 cores, 
> 4G ram.  But I haven't rebooted to it yet.  Next good excuse.  See below... :)

I guess you can only use 3G ram because there is a big memory hole.
Your HighMem zone spanned 951810 pages, 813013 of which is present.
So it's not quite accurate for the OOM message "951810 pages HighMem"
to report the spanned pages.

Your Normal zone has 221994 present pages, while the OOM message shows
"slab:206505", which indicates that the OOM is caused by too much
slab pages(they cannot be allocated from HighMem zone).

I guess your near 800MB slab cache is somehow under scanned.

Thanks,
Fengguang

--
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>

  reply	other threads:[~2009-07-08  5:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200907061056.00229.gene.heskett@verizon.net>
2009-07-07  6:12 ` OOM killer in 2.6.31-rc2 Wu Fengguang
2009-07-07 14:57   ` Gene Heskett
2009-07-08  2:17     ` Wu Fengguang
2009-07-08  3:42       ` Gene Heskett
2009-07-08  5:15         ` Wu Fengguang [this message]
2009-07-08  7:55           ` Wu Fengguang
2009-07-08 14:22             ` Gene Heskett
2009-07-09 14:42             ` Gene Heskett
2009-07-09 20:41               ` John Stoffel
2009-07-09 21:03                 ` Gene Heskett
2009-07-10 13:09                   ` John Stoffel
2009-07-10 13:18                     ` Wu Fengguang
2009-07-10 13:24                   ` Wu Fengguang
     [not found] ` <200907101100.58110.gene.heskett@verizon.net>
     [not found]   ` <20090711083551.GA6209@localhost>
     [not found]     ` <200907110819.30337.gene.heskett@verizon.net>
2009-07-12  5:14       ` Wu Fengguang
2009-07-14  4:10         ` Gene Heskett

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=20090708051515.GA17156@localhost \
    --to=fengguang.wu@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=gene.heskett@verizon.net \
    --cc=kernel-testers@vger.kernel.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan.kim@gmail.com \
    --cc=rjw@sisk.pl \
    /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;
as well as URLs for NNTP newsgroup(s).