From: Andrew Morton <akpm@osdl.org>
To: Steve Lord <lord@xfs.org>
Cc: ak@suse.de, linux-kernel@vger.kernel.org, kenneth.w.chen@intel.com
Subject: Re: Limit hash table size
Date: Thu, 5 Feb 2004 19:12:40 -0800 [thread overview]
Message-ID: <20040205191240.13638135.akpm@osdl.org> (raw)
In-Reply-To: <4021AC9F.4090408@xfs.org>
Steve Lord <lord@xfs.org> wrote:
>
> I have seen some dire cases with the dcache, SGI had some boxes with
> millions of files out there, and every night a cron job would come
> along and suck them all into memory. Resources got tight at some point,
> and as more inodes and dentries were being read in, the try to free
> pages path was continually getting called. There was always something
> in filesystem cache which could get freed, and the inodes and dentries
> kept getting more and more of the memory.
There are a number of variables here. Certainly, the old
inodes-pinned-by-highmem pagecache will cause this to happen - badly. 2.6
is pretty aggressive at killing off those inodes.
What kernel was it?
Was it a highmem box? If so, was the filesystem in question placing
directory pagecache in highmem? If so, that was really bad on older 2.4:
the directory pagecache in highmem pins down all directory inodes.
next prev parent reply other threads:[~2004-02-06 3:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B05667366EE6204181EABE9C1B1C0EB5802441@scsmsx401.sc.intel.com.suse.lists.linux.kernel>
[not found] ` <20040205155813.726041bd.akpm@osdl.org.suse.lists.linux.kernel>
2004-02-06 1:54 ` Andi Kleen
2004-02-05 2:38 ` Steve Lord
2004-02-06 3:12 ` Andrew Morton [this message]
2004-02-05 4:06 ` Steve Lord
2004-02-06 4:39 ` Andi Kleen
2004-02-06 4:59 ` Andrew Morton
2004-02-06 5:34 ` Maneesh Soni
2004-02-06 3:19 ` Andi Kleen
2004-02-06 3:23 ` Nick Piggin
2004-02-06 3:34 ` Andrew Morton
2004-02-06 3:38 ` Nick Piggin
2004-02-18 12:41 ` Pavel Machek
2004-02-06 3:09 ` Andrew Morton
2004-02-06 3:18 ` Andi Kleen
2004-02-06 3:30 ` Andrew Morton
2004-02-06 4:45 ` Martin J. Bligh
2004-02-06 6:22 ` Matt Mackall
2004-02-06 20:20 ` Taneli Vähäkangas
2004-02-06 20:27 ` Andrew Morton
2004-02-06 21:46 ` Taneli Vähäkangas
2004-02-18 0:45 Chen, Kenneth W
-- strict thread matches above, loose matches on Subject: below --
2004-02-18 0:16 Chen, Kenneth W
2004-02-17 22:24 Chen, Kenneth W
2004-02-17 23:24 ` Andrew Morton
2004-02-06 6:32 Manfred Spraul
2004-02-06 0:10 Chen, Kenneth W
2004-02-06 0:23 ` Andrew Morton
2004-02-09 23:12 ` Jes Sorensen
2004-01-14 22:31 Chen, Kenneth W
2004-01-18 14:25 ` Anton Blanchard
2004-01-14 22:29 Chen, Kenneth W
2004-01-12 16:50 Manfred Spraul
2004-01-09 19:05 Chen, Kenneth W
2004-01-12 13:32 ` Anton Blanchard
2004-01-08 23:12 Chen, Kenneth W
2004-01-09 9:25 ` Andrew Morton
2004-01-09 14:25 ` Anton Blanchard
2004-02-05 23:58 ` Andrew Morton
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=20040205191240.13638135.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lord@xfs.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
all inboxes | Powered by JetHome®