From: J Sloan <jjs@lexus.com>
To: brian@worldcontrol.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.17 vs 2.2.19 vs rml new VM
Date: Wed, 02 Jan 2002 11:07:35 -0800 [thread overview]
Message-ID: <3C335A77.806@lexus.com> (raw)
In-Reply-To: <20020102013305.A5272@top.worldcontrol.com>
Just .02 from the peanut gallery -
It would be interesting if you were to compare and
contrast 2.4.17-preempt with 2.4.17-low-latency.
I find the low latency patch makes a noticeable
difference in e.g. q3a and rtcw - OTOH I have
not been able to discern any tangible difference
from the stock kernel when using -preempt.
cu
jjs
brian@worldcontrol.com wrote:
>I'd like to say that as of 2.4.17 w/preempt patch, the linux kernel
>seems again to perform as well as 2.2.19 for interactive use and
>reliability, at least in my use.
>
>2.4.17 still croaks running some of the giant memory applications
>that I run successfully on 2.2.19. (Machines with 2GB of RAM
>running 3GB+ apps.)
>
>I tried rmap-10 new VM and under my typical load my desktop machine
>froze repeatedly. Seemed the memory pool was going down the drain
>before the freeze. Meaning apps were failing and getting stuck in
>various odd states.
>
>No doubt, preempt and rmap-10 are incompatible, but I'm not going to
>give up the preempt patch any time soon.
>
>All in all 2.4.17 w/preempt is very satisfactory.
>
next prev parent reply other threads:[~2002-01-02 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-02 9:33 Linux 2.4.17 vs 2.2.19 vs rml new VM brian
2002-01-02 10:07 ` Alan Cox
2002-01-02 12:25 ` Rik van Riel
2002-01-02 19:07 ` J Sloan [this message]
2002-01-02 20:50 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-01-02 23:14 Dieter Nützel
2002-01-02 23:49 ` J Sloan
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=3C335A77.806@lexus.com \
--to=jjs@lexus.com \
--cc=brian@worldcontrol.com \
--cc=linux-kernel@vger.kernel.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