From: Rik van Riel <riel@conectiva.com.br>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH *] rmap VM 11c
Date: Thu, 17 Jan 2002 22:05:52 -0200 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.33L.0201172204080.32617-100000@imladris.surriel.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1020117185411.4089A-100000@gatekeeper.tmr.com>
On Thu, 17 Jan 2002, Bill Davidsen wrote:
> > http://surriel.com/patches/2.4/2.4.17-rmap-11c
> > and http://linuxvm.bkbits.net/
> Rik, I tried a simple test, building a kernel in a 128M P-II-400, and
> when the load average got up to 50 or so the system became slow;-) On
> the other hand it was still usable for most normal things other then
> incoming mail which properly blocks at LA>10 or so.
Hehehe, when the load average is 50 only 2% of the CPU is available
for you. With that many gccs you're also under a memory squeeze with
128 MB of RAM, so it's no big wonder things got slow. ;)
I'm happy to hear the system was still usable, though.
> I'll be trying it on a large machine tomorrow, but it at least looks
> stable. In real life no sane person would do that, would they? Make
> with a nice -10 was essentially invisible.
Neat ...
> Maybe tomorrow the lateest -aa kernel on the same machine, with and
> without my own personal patch.
Looking forward to the results.
regards,
Rik
--
"Linux holds advantages over the single-vendor commercial OS"
-- Microsoft's "Competing with Linux" document
http://www.surriel.com/ http://distro.conectiva.com/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-01-18 0:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 19:22 Rik van Riel
2002-01-17 23:59 ` Bill Davidsen
2002-01-18 0:05 ` Rik van Riel [this message]
2002-01-18 0:33 ` Adam Kropelin
2002-01-18 0:56 ` Rik van Riel
2002-01-18 10:06 ` Roy Sigurd Karlsbakk
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.4.33L.0201172204080.32617-100000@imladris.surriel.com \
--to=riel@conectiva.com.br \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--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