From: Nick Piggin <piggin@cyberone.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: lord@xfs.org, ak@suse.de, linux-kernel@vger.kernel.org,
kenneth.w.chen@intel.com
Subject: Re: Limit hash table size
Date: Fri, 06 Feb 2004 14:38:49 +1100 [thread overview]
Message-ID: <40230C49.4010803@cyberone.com.au> (raw)
In-Reply-To: <20040205193449.5a8b8c0b.akpm@osdl.org>
Andrew Morton wrote:
>Nick Piggin <piggin@cyberone.com.au> wrote:
>
>>>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.
>> >
>> >
>>
>> 2.6.2-mm1 should fix this I think.
>>
>
>2.6.anything should fix it. It used to, anyway.
>
>
>> In particular, this hunk in vm-shrink-zone.patch
>>
>
>That's on the direct reclaim path - for sane workloads most of the freeing
>activity is via kswapd.
>
>
>
OK - he said the try to free pages path was being called but
maybe he didn't actually mean try_to_free_pages.
next prev parent reply other threads:[~2004-02-06 3:38 UTC|newest]
Thread overview: 54+ 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 ` Limit hash table size Andi Kleen
2004-02-05 2:38 ` Steve Lord
2004-02-06 3:12 ` Andrew Morton
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 [this message]
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-06 6:32 Manfred Spraul
-- strict thread matches above, loose matches on Subject: below --
2004-01-12 16:50 Manfred Spraul
2004-01-08 23:12 Chen, Kenneth W
2004-01-08 23:12 ` Chen, Kenneth W
2004-01-09 9:25 ` Andrew Morton
2004-01-09 9:25 ` Andrew Morton
2004-01-09 14:25 ` Anton Blanchard
2004-01-09 14:25 ` Anton Blanchard
2004-01-09 19:05 ` Chen, Kenneth W
2004-01-09 19:05 ` Chen, Kenneth W
2004-01-12 13:32 ` Anton Blanchard
2004-01-12 13:32 ` Anton Blanchard
2004-01-14 22:29 ` Chen, Kenneth W
2004-01-14 22:29 ` Chen, Kenneth W
2004-01-14 22:31 ` Chen, Kenneth W
2004-01-14 22:31 ` Chen, Kenneth W
2004-01-18 14:25 ` Anton Blanchard
2004-01-18 14:25 ` Anton Blanchard
2004-02-05 23:58 ` Andrew Morton
2004-02-05 23:58 ` Andrew Morton
2004-02-06 0:10 ` Chen, Kenneth W
2004-02-06 0:10 ` Chen, Kenneth W
2004-02-06 0:23 ` Andrew Morton
2004-02-06 0:23 ` Andrew Morton
2004-02-09 23:12 ` Jes Sorensen
2004-02-09 23:12 ` Jes Sorensen
2004-02-17 22:24 ` Chen, Kenneth W
2004-02-17 22:24 ` Chen, Kenneth W
2004-02-17 23:24 ` Andrew Morton
2004-02-17 23:24 ` Andrew Morton
2004-02-18 0:16 ` Chen, Kenneth W
2004-02-18 0:16 ` Chen, Kenneth W
2004-02-18 0:45 ` Chen, Kenneth W
2004-02-18 0:45 ` Chen, Kenneth W
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=40230C49.4010803@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--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 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.