From: Linus Torvalds <torvalds@transmeta.com>
To: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH] swapout speedup 2.1.91-pre2
Date: Thu, 26 Mar 1998 09:39:11 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.3.95.980326093755.32429H-100000@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.3.91.980326121934.19975A-100000@mirkwood.dummy.home>
On Thu, 26 Mar 1998, Rik van Riel wrote:
>
> here's the speedup patch I promised earlier.
> It:
> - increases tries when we're tight on memory
> - clusters swapouts from user programs (to save disk movement)
> - wraps the above in a nice inline
>
> NOTE: this patch is untested, but otherwise completely trivial :)
Ok, this looks more like the kind of algorithms I wanted. I alread knew
that the hardcoded "50" was wrong, your heuristic looks sensible (with the
modification you already sent to make it slightly less aggressive).
Anyway, I'm fairly happy with this kind of setup, I'll make a real 2.1.91
soonish,
Linus
next prev parent reply other threads:[~1998-03-26 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-26 11:22 Rik van Riel
1998-03-26 17:39 ` Linus Torvalds [this message]
1998-03-26 18:54 ` Rik van Riel
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.95.980326093755.32429H-100000@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=H.H.vanRiel@fys.ruu.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox