From: Hugh Dickins <hugh@veritas.com>
To: Andrew Morton <akpm@osdl.org>
Cc: kmannth@us.ibm.com, linux-mm@kvack.org
Subject: Re: [Bug 3268] New: Lowmemory exhaustion problem with v2.6.8.1-mm4 16gb
Date: Wed, 25 Aug 2004 00:20:26 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.44.0408242352470.2713-100000@localhost.localdomain> (raw)
In-Reply-To: <20040824144312.09b4af42.akpm@osdl.org>
On Tue, 24 Aug 2004, 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
> > 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...
>
> I assume this is because we're using up all of lowmem with filesystem metadata.
>
> Hugh?
Probably, though it's not something anyone reported before.
Filesystem metadata being, not tmpfs's indirect blocks (which use highmem),
but the plenitude of inodes and dentries: which would get pruned if it were
a disk-based filesystem, but cannot because this one is all in memory.
I've not done the arithmetic... tomorrow. I'll try to reproduce something
similar (I don't have 16GB and I don't have NUMA, though latter probably
not relevant) tomorrow, and fix (decide default nr_inodes by lowmem).
Keith, please do mail me your script (in case there's something special
in there e.g. will make a difference if your sources are linked or not),
and also your /proc/slabinfo near OOMing, if that's convenient.
Thanks,
Hugh
--
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>
next prev parent reply other threads:[~2004-08-24 23:20 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
2004-08-24 23:24 ` Andrew Morton
2004-08-24 23:20 ` Hugh Dickins [this message]
[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=Pine.LNX.4.44.0408242352470.2713-100000@localhost.localdomain \
--to=hugh@veritas.com \
--cc=akpm@osdl.org \
--cc=kmannth@us.ibm.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