From: "Dr. Werner Fink" <werner@suse.de>
To: Linux Kernel <linux-kernel@vger.rutgers.edu>
Cc: linux-mm@kvack.org
Subject: Re: 2.1.110 freepages.min change
Date: Wed, 22 Jul 1998 22:27:36 +0200 [thread overview]
Message-ID: <19980722222736.49195@boole.suse.de> (raw)
In-Reply-To: <Pine.LNX.3.96.980722181024.13036A-100000@mirkwood.dummy.home>; from Rik van Riel on Wed, Jul 22, 1998 at 06:12:37PM +0200
On Wed, Jul 22, 1998 at 06:12:37PM +0200, Rik van Riel wrote:
> Hi Linus,
>
> I've noticed that, in 2.1.110, the value for the
> minimum amount of free pages changed from 48 to
> 10.
>
> Considering the amount of fragmentation problems
> observed and the numbers generated by your fragmentation
> calculation program, this seems a tad on the low side...
>
> If fragmentation problems show up, I suggest we up this
> limit again...
>
It seem's that if the limit is reached now the new try_to_free_pages
instead of the old try_to_free_page(without s) function may free some
more pages as requested ... in best case SWAP_CLUSTER_MAX pages are
freed at once ... looks good Linus. Together with the increased
count_max and count_min in shrink_mmap this one really makes sense.
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
PS: I've updated my lowmem.patch to 2.1.110. I would like to
hear some comments on it ... for more please see
http://www.suse.de/~werner/patches/
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next parent reply other threads:[~1998-07-22 20:28 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 [this message]
1998-07-23 14:43 ` 2.1.110 freepages.min change Stephen C. Tweedie
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=19980722222736.49195@boole.suse.de \
--to=werner@suse.de \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.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.