From: Andrew Morton <akpm@digeo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm mailing list <linux-mm@kvack.org>
Subject: Re: ZONE_NORMAL exhaustion (dcache slab)
Date: Mon, 21 Oct 2002 14:33:42 -0700 [thread overview]
Message-ID: <3DB472B6.BC5B8924@digeo.com> (raw)
In-Reply-To: 308170000.1035234988@flay
"Martin J. Bligh" wrote:
>
> >> My big NUMA box went OOM over the weekend and started killing things
> >> for no good reason (2.5.43-mm2). Probably running some background
> >> updatedb for locate thing, not doing any real work.
> >>
> >> meminfo:
> >>
> >
> > Looks like a plain dentry leak to me. Very weird.
> >
> > Did the machine recover and run normally?
>
> Nope, kept OOMing and killing everything .
Something broke.
> > Was it possible to force the dcache to shrink? (a cat /dev/hda1
> > would do that nicely)
>
> Well, I didn't try that, but even looking at man pages got oom killed,
> so I guess not ... were you looking at the cat /dev/hda1 to fill pagecache
> or something? I have 16Gb of highmem (pretty much all ununsed) so
> presumably that'd fill the highmem first (pagecache?)
Blockdevices only use ZONE_NORMAL for their pagecache. That cat will
selectively put pressure on the normal zone (and DMA zone, of course).
> > Is it reproducible?
>
> Will try again. Presumably "find /" should do it? ;-)
You must have a lot of files.
Actually, I expect a `find /' will only stat directories,
whereas an `ls -lR /' will stat plain files as well. Same
thing for dcache, but the ls will push the icache harder.
I don't know if updatedb stats regular files. Presumably not.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@digeo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm mailing list <linux-mm@kvack.org>
Subject: Re: ZONE_NORMAL exhaustion (dcache slab)
Date: Mon, 21 Oct 2002 14:33:42 -0700 [thread overview]
Message-ID: <3DB472B6.BC5B8924@digeo.com> (raw)
In-Reply-To: 308170000.1035234988@flay
"Martin J. Bligh" wrote:
>
> >> My big NUMA box went OOM over the weekend and started killing things
> >> for no good reason (2.5.43-mm2). Probably running some background
> >> updatedb for locate thing, not doing any real work.
> >>
> >> meminfo:
> >>
> >
> > Looks like a plain dentry leak to me. Very weird.
> >
> > Did the machine recover and run normally?
>
> Nope, kept OOMing and killing everything .
Something broke.
> > Was it possible to force the dcache to shrink? (a cat /dev/hda1
> > would do that nicely)
>
> Well, I didn't try that, but even looking at man pages got oom killed,
> so I guess not ... were you looking at the cat /dev/hda1 to fill pagecache
> or something? I have 16Gb of highmem (pretty much all ununsed) so
> presumably that'd fill the highmem first (pagecache?)
Blockdevices only use ZONE_NORMAL for their pagecache. That cat will
selectively put pressure on the normal zone (and DMA zone, of course).
> > Is it reproducible?
>
> Will try again. Presumably "find /" should do it? ;-)
You must have a lot of files.
Actually, I expect a `find /' will only stat directories,
whereas an `ls -lR /' will stat plain files as well. Same
thing for dcache, but the ls will push the icache harder.
I don't know if updatedb stats regular files. Presumably not.
--
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/
next prev parent reply other threads:[~2002-10-21 21:27 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 20:40 ZONE_NORMAL exhaustion (dcache slab) Martin J. Bligh
2002-10-21 20:40 ` Martin J. Bligh
2002-10-21 21:13 ` Andrew Morton
2002-10-21 21:13 ` Andrew Morton
2002-10-21 21:16 ` Martin J. Bligh
2002-10-21 21:16 ` Martin J. Bligh
2002-10-21 21:33 ` Andrew Morton [this message]
2002-10-21 21:33 ` Andrew Morton
2002-10-21 21:33 ` Martin J. Bligh
2002-10-21 21:33 ` Martin J. Bligh
2002-10-21 21:49 ` Andrew Morton
2002-10-21 21:49 ` Andrew Morton
2002-10-21 22:30 ` Rik van Riel
2002-10-21 22:30 ` Rik van Riel
2002-10-21 22:53 ` Andrew Morton
2002-10-21 22:53 ` Andrew Morton
2002-10-22 0:31 ` Martin J. Bligh
2002-10-22 0:31 ` Martin J. Bligh
2002-10-22 3:39 ` Andrew Morton
2002-10-22 3:39 ` Andrew Morton
2002-10-22 3:53 ` Martin J. Bligh
2002-10-22 3:53 ` Martin J. Bligh
2002-10-22 4:20 ` Andrew Morton
2002-10-22 4:20 ` Andrew Morton
2002-10-22 5:49 ` Martin J. Bligh
2002-10-22 5:49 ` Martin J. Bligh
2002-10-22 6:21 ` Andrew Morton
2002-10-22 6:21 ` Andrew Morton
2002-10-22 16:13 ` Martin J. Bligh
2002-10-22 16:13 ` Martin J. Bligh
2002-10-24 11:35 ` Ed Tomlinson
2002-10-24 11:35 ` Ed Tomlinson
2002-10-24 14:28 ` Martin J. Bligh
2002-10-24 14:28 ` Martin J. Bligh
2002-10-22 16:33 ` Rik van Riel
2002-10-22 16:33 ` Rik van Riel
2002-10-22 16:54 ` ARP address resolving in kernel Steffen Persvold
2002-10-22 17:05 ` ZONE_NORMAL exhaustion (dcache slab) Andrew Morton
2002-10-22 17:05 ` Andrew Morton
2002-10-22 16:21 ` Dipankar Sarma
2002-10-22 16:21 ` Dipankar Sarma
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=3DB472B6.BC5B8924@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.