From: "Anish Srivastava" <anishs@vsnl.com>
To: "Andrew Morton" <akpm@zip.com.au>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
"Andrea Arcangeli" <andrea@suse.de>,
"Rik van Riel" <riel@conectiva.com.br>,
<alan@lxorguk.ukuu.org.uk>
Subject: Re: kernel 2.4.17 with -rmap VM patch ROCKS!!!
Date: Fri, 25 Jan 2002 14:02:58 +0530 [thread overview]
Message-ID: <018401c1a57a$e8102590$3c00a8c0@baazee.com> (raw)
In-Reply-To: <008301c1a4c1$a79f8fa0$3c00a8c0@baazee.com> <3C5076C1.DDEE200B@zip.com.au>
> The fact that the current stable version of the Linux kernel
> can only achieve an eight-hour uptime on this class of machine
> is a fairly serious problem, don't we all agree?
>
> We need a fix for 2.4.18.
>
> Did you test the -aa patches?
No, I havent tried the aa patches. I belive the aa patches are to be
integrated in the 2.4.18 official stable release.
Since I am quite happy with the performance of my machine with
the rmap patch......I will leave it as it is. Though, for your information
I will be checking out the aa patches on my backup machine
which is also of the same class. I will let you guys know the
performance with the aa patches incorporated as soon as
I set it up on the other machine.
Regards,
Anish
next prev parent reply other threads:[~2002-01-25 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 10:26 kernel 2.4.17 with -rmap VM patch ROCKS!!! Anish Srivastava
2002-01-24 21:04 ` Andrew Morton
2002-01-25 8:32 ` Anish Srivastava [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-24 11:17 Anish Srivastava
2002-01-26 16:23 Stolle, Martin (KIV)
2002-01-26 17:36 ` Roland Arendes
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='018401c1a57a$e8102590$3c00a8c0@baazee.com' \
--to=anishs@vsnl.com \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
/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