From: Chris Wedgwood <cw@f00f.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 inode cache eats system, news at 11
Date: Mon, 26 Apr 2004 10:58:25 -0700 [thread overview]
Message-ID: <20040426175825.GA31202@dingdong.cryptoapps.com> (raw)
In-Reply-To: <20040426171856.22514.qmail@lwn.net>
On Mon, Apr 26, 2004 at 11:18:56AM -0600, Jonathan Corbet wrote:
> Of my 800MB of slab use, those two are responsible for 755MB.
I see this too sometimes. Basically slab grows insanely large and you
run out of lowmem and all turns crappy. Even with 64-bit arch's like
yours the sab can still get out of hand, I've seen 5GB used on an 8GB
machine.
It's not ext3 specific, other filesystems can and will do this too.
--cw
next prev parent reply other threads:[~2004-04-26 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 17:18 ext3 inode cache eats system, news at 11 Jonathan Corbet
2004-04-26 17:58 ` Chris Wedgwood [this message]
2004-04-27 1:12 ` Andrew Morton
2004-04-27 3:26 ` Nick Piggin
2004-04-27 4:02 ` Andrew Morton
2004-04-27 4:17 ` Nick Piggin
2004-04-28 10:41 ` Jose R. Santos
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=20040426175825.GA31202@dingdong.cryptoapps.com \
--to=cw@f00f.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.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