linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: keith <kmannth@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-mm@kvack.org, Hugh Dickins <hugh@veritas.com>
Subject: Re: [Bug 3268] New: Lowmemory exhaustion problem with v2.6.8.1-mm4 16gb
Date: Tue, 24 Aug 2004 16:11:07 -0700	[thread overview]
Message-ID: <1093389067.5677.1839.camel@knk> (raw)
In-Reply-To: <20040824144312.09b4af42.akpm@osdl.org>

On Tue, 2004-08-24 at 14:43, Andrew Morton wrote:
> bugme-daemon@osdl.org wrote:
> >
> > http://bugme.osdl.org/show_bug.cgi?id=3268
> > 
> >            Summary: Lowmemory exhaustion problem with v2.6.8.1-mm4 16gb
> >     Kernel Version:  2.6.8.1-mm4
> >             Status: NEW
> >           Severity: high
> >              Owner: akpm@digeo.com
> >          Submitter: kmannth@us.ibm.com
> >                 CC: mbligh@aracnet.com
> > 
> > 
> > Distribution:  SuSE SLES9 base
> > Hardware Environment:  IBM x445 8-way  32gb and 16 gb 
> > Software Environment:   2.6.8.1-mm4
> > Problem Description:  I run out of lowmemory very easily using /dev/shm/
> > I have 64g and Numa/Discontig enabled in my kernel.  
> > 
> > Steps to reproduce:  Fill up 1/2 or more of /dev/shm (on my system it is about
> > 1/3-1/2 of my total system memory) with lots of kernel builds.  Observe system
> > breakdown.  (If you want the script I will email it to you).  I have seen this
> > with both 32 gigs and 16 gigs...
> > 
> > For example if I boot with 16gb and I start 45 kernel builds in /dev/shm they
> > system take about 30-60 seconds to run out of lowmemory.  
> > The oom killer comes in and starts shutting down processes.  The system is unsuable.
> >   There is tons of highmem left but no lowmem.  Is there something about
> > /dev/shm that might cause this? 
> > 
> > I turned some various vm debug optoins that printed out some info that I will
> > attach.  I will attach the config file and as much of the kernel messages as I
> > can.
> 
> I assume this is because we're using up all of lowmem with filesystem metadata.
> 
> Hugh?
> 

As a note. I am able to run this test with Reiser just fine.  It looks
like the shmfs code always calls kmem_cache_alloc when it needs to
allocate a new inode.  
  If the kmem_cache_alloc calls are filling up lowmem shouldn't the
alloc calls fail eventually instead of sending out the oom killer to all
the processes in the system?  Is it possible to fail an kmem_cache_alloc
call?
  
Keith Mannthey

--
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:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2004-08-24 23:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200408242051.i7OKplP0009870@fire-1.osdl.org>
2004-08-24 21:43 ` Andrew Morton
2004-08-24 23:11   ` keith [this message]
2004-08-24 23:24     ` Andrew Morton
2004-08-24 23:20   ` Hugh Dickins
     [not found] <1093400029.5677.1866.camel@knk>
2004-08-25 14:05 ` Hugh Dickins
2004-08-25 19:05   ` keith
2004-08-25 20:37     ` Hugh Dickins
2004-08-25 20:53       ` Andrew Morton
2004-08-25 20:59         ` Hugh Dickins
2004-08-25 21:19         ` Martin J. Bligh
2004-08-25 21:35           ` Andrew Morton
2004-08-25 21:49       ` keith
2004-08-25 22:02         ` Martin J. Bligh
2004-08-26 15:28         ` Hugh Dickins

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=1093389067.5677.1839.camel@knk \
    --to=kmannth@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.com \
    --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