From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Dr. Werner Fink" <werner@suse.de>
Cc: Linux Kernel <linux-kernel@vger.rutgers.edu>, linux-mm@kvack.org
Subject: Re: 2.1.110 freepages.min change
Date: Thu, 23 Jul 1998 15:43:11 +0100 [thread overview]
Message-ID: <199807231443.PAA08910@dax.dcs.ed.ac.uk> (raw)
In-Reply-To: <19980722222736.49195@boole.suse.de>
On Wed, 22 Jul 1998 22:27:36 +0200, "Dr. Werner Fink" <werner@suse.de> said:
> The change in fs/dcache.c does not look very well because
> as higher the number given to prune_dache in shrink_dcache_memory
> as more the dcache is pruned ... `0' isn't that good is it?
Werner, have you given it a shot? With this fix in place, the
dcache/inode fragmentation issues in 2.1 are very dramatically improved
on low memory. I'm very pleased indeed with this patch: even if it's
only prune_dcache(0), it is still being called much more often when we
get short of memory.
--Stephen
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
prev parent reply other threads:[~1998-07-23 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.96.980722181024.13036A-100000@mirkwood.dummy.home>
1998-07-22 20:27 ` Dr. Werner Fink
1998-07-23 14:43 ` Stephen C. Tweedie [this message]
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=199807231443.PAA08910@dax.dcs.ed.ac.uk \
--to=sct@redhat.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=werner@suse.de \
/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