linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: keith <kmannth@us.ibm.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-mm@kvack.org
Subject: Re: [Bug 3268] New: Lowmemory exhaustion problem with v2.6.8.1-mm4 16gb
Date: Wed, 25 Aug 2004 12:05:01 -0700	[thread overview]
Message-ID: <1093460701.5677.1881.camel@knk> (raw)
In-Reply-To: <Pine.LNX.4.44.0408251448370.4332-100000@localhost.localdomain>

On Wed, 2004-08-25 at 07:05, Hugh Dickins wrote:
> On Tue, 24 Aug 2004, keith wrote:
> > 
> > Ok I created an attachment in the bug for the slab/buddy/mem info.  
> > You can watch zone normal get exhausted :)
> > http://bugme.osdl.org/show_bug.cgi?id=3268
> 
> Thanks.  Yes, your lowmem is full of Slab, and that's entirely
> unsurprising since you have CONFIG_DEBUG_PAGEALLOC on: so every
> slab object needs a full 4096-byte page to itself (well, there
> are some exceptions, but that doesn't change the picture).
> 
> That's a _very_ distorting config option, and I think this means that
> your report is of no interest in itself - sorry.  But it does raise a
> valid question whether it can happen in real, non-debug life - thanks.

I turned CONFIG_DEBUG_PAGEALLOC off.  I ran into problems when I tried
building 60 kernel trees or so.  It is using about 10gb of tmpfs space. 
See http://bugme.osdl.org/attachment.cgi?id=3566&action=view for more
info.

The bug also contains the config file used.  
> 
> I'll do the arithmetic on that when I've more leisure: I expect the
> answer to be that it can happen, and I ought to adjust defaulting of
> maximum tmpfs inodes.

It looks like there should be a maximum number of inodes for tmpfs.
Because I didn't know how many inodes it is using but I gave it a large
playground to use (mount -t tmpfs -o size=15G,nr_inodes=10000k,mode=0700
tmpfs /mytmpfs)

Thanks,
  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-25 19:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1093400029.5677.1866.camel@knk>
2004-08-25 14:05 ` Hugh Dickins
2004-08-25 19:05   ` keith [this message]
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
     [not found] <200408242051.i7OKplP0009870@fire-1.osdl.org>
2004-08-24 21:43 ` Andrew Morton
2004-08-24 23:11   ` keith
2004-08-24 23:24     ` Andrew Morton
2004-08-24 23:20   ` 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=1093460701.5677.1881.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