From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: "Stephen C. Tweedie" <sct@dcs.ed.ac.uk>
Cc: Linus Torvalds <torvalds@transmeta.com>,
"Benjamin C.R. LaHaise" <blah@kvack.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: [uPATCH] small kswapd improvement ???
Date: Wed, 4 Mar 1998 00:59:33 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.3.91.980304005820.5443F-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <199803032354.XAA02829@dax.dcs.ed.ac.uk>
On Tue, 3 Mar 1998, Stephen C. Tweedie wrote:
> > I remember the 1.1 or 1.2 days when Stephen reworked the
> > swap code and I played around with a small piece of
> > vmscan.c. Back then a simple bug was encountered and 'fixed'
> > by always starting the memory scan at adress 0, which gives
> > a highly unfair and inefficient aging process.
>
> Ouch --- I wonder how much this is hurting 2.0.33. I think I'll have
> to try that, and perhaps look at this for 2.0.34/LMP...
It doesn't hurt _that_ much... Otherwise we wouldn't
have left it in the swapper code for three years :-)
It gives somewhat more than a smallish improvement
though...
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/ |
+-----------------------------+------------------------------+
next prev parent reply other threads:[~1998-03-03 23:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-03 17:05 Rik van Riel
1998-03-03 19:09 ` Rik van Riel
1998-03-03 23:54 ` Stephen C. Tweedie
1998-03-03 23:59 ` Rik van Riel [this message]
1998-03-04 1:17 ` Benjamin C.R. LaHaise
1998-03-04 11:54 ` Rik van Riel
1998-03-04 21:11 ` Stephen C. Tweedie
1998-03-04 23:27 ` Rik van Riel
1998-03-04 14:00 ` Dr. Werner Fink
1998-03-04 15:33 ` 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.91.980304005820.5443F-100000@mirkwood.dummy.home \
--to=h.h.vanriel@fys.ruu.nl \
--cc=blah@kvack.org \
--cc=linux-mm@kvack.org \
--cc=sct@dcs.ed.ac.uk \
--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