From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: [docPATCH] vm.txt change
Date: Tue, 10 Mar 1998 16:29:18 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.3.91.980310162545.20757A-100000@mirkwood.dummy.home> (raw)
Hi Linus,
In the light of 'help, my 32meg system has 60megs of
buffermem' I decided to update
linux/Documentation/sysctl/vm.txt
in order to help out the people who are experiencing
those problems.
And to the people who are experiencing those problems:
RTFM :-)
Rik.
+-------------------------------------------+--------------------------+
| Linux: - LinuxHQ MM-patches page | Scouting webmaster |
| - kswapd ask-him & complain-to guy | Vries cubscout leader |
| http://www.fys.ruu.nl/~riel/ | <H.H.vanRiel@fys.ruu.nl> |
+-------------------------------------------+--------------------------+
--- linux/Documentation/sysctl/vm.txt~ Tue Mar 10 16:24:40 1998
+++ linux/Documentation/sysctl/vm.txt Tue Mar 10 16:24:40 1998
@@ -164,7 +164,7 @@
swapctl:
This file contains no less than 16 variables, of which about
-half is actually used :-) In the listing below, the unused
+half are actually used :-) In the listing below, the unused
variables are marked as such.
All of these values are used by kswapd, and the usage can be
found in linux/mm/vmscan.c.
@@ -221,9 +221,12 @@
The values of sc_pageout_weight and sc_bufferout_weight are
used to control the how many tries kswapd will do in order
-to swapout one page / buffer. As with sc_age_cluster_fract,
-the actual value is calculated by several more or less complex
-formulae and the default value is good for every purpose.
+to swapout one page / buffer. These values can be used to
+finetune the ratio between user pages and buffer/cache memory.
+When you find that your Linux system is swapping out too much
+process pages in order to satisfy buffer memory demands, you
+might want to either increase sc_bufferout_weight, or decrease
+the value of sc_pageout_weight.
==============================================================
reply other threads:[~1998-03-10 17:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.3.91.980310162545.20757A-100000@mirkwood.dummy.home \
--to=h.h.vanriel@fys.ruu.nl \
--cc=linux-mm@kvack.org \
--cc=torvalds@transmeta.com \
/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