From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-mm <linux-mm@kvack.org>
Subject: Re: swapout frenzy solution
Date: Thu, 5 Mar 1998 22:49:19 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.3.91.980305224225.1206A-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <Pine.LNX.3.91.980305221552.448A-100000@mirkwood.dummy.home>
On Thu, 5 Mar 1998, Rik van Riel wrote:
> I've just come up with a simple 'solution' for the swapout
> frenzy experienced by the recent free_memory_available()
> test in kswapd.
Hate to follow up to my own posts, but here it goes:
Once my system reached a state where it needed to
free a _large_ (MAX_ORDER) area, nr_free_pages kept
lingering around free_pages_high * 4 :-(
This means that this scheme doesn't really work...
Then I've got another possible solution. In try_to_swap_out,
we:
- test what page-order this page is holding up
- change the following:
if (page->age)
- into:
if (page->age - order_block(page))
This means that a page blocking an order-5 area will
be heavily penalized for this, so this page will be
freed earlier than other pages (which don't occupy
'critical' regions.
Of course, reserving 1/16th of memory for exclusive
use by the page and buffer cache (which we can already
clean on a page-by-page basis) will be far superior
to this...
I don't have time to code this up before the weekend,
so you've got all the time to decide which solution
you'd like to see implemented...
Rik.
+-----------------------------+------------------------------+
| For Linux mm-patches, go to | "I'm busy managing memory.." |
| my homepage (via LinuxHQ). | H.H.vanRiel@fys.ruu.nl |
| ...submissions welcome... | http://www.fys.ruu.nl/~riel/ |
+-----------------------------+------------------------------+
prev parent reply other threads:[~1998-03-05 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-05 21:22 Rik van Riel
1998-03-05 21:49 ` Rik van Riel [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=Pine.LNX.3.91.980305224225.1206A-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