From: Andrea Arcangeli <andrea@suse.de>
To: Aviv Shavit <avivshavit@yahoo.com>
Cc: Ken Brownfield <brownfld@irridia.com>, linux-kernel@vger.kernel.org
Subject: vm-33, strongly recommended [Re: [2.4.17/18pre] VM and swap - it's really unusable]
Date: Wed, 10 Apr 2002 01:36:09 +0200 [thread overview]
Message-ID: <20020410013609.A6875@dualathlon.random> (raw)
In-Reply-To: <20020225224050.D26077@asooo.flowerfire.com> <20020409204545.11251.qmail@web13205.mail.yahoo.com>
I recommend everybody to never use a 2.4 kernel without first applying
this vm patch:
ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/patches/v2.4/2.4.19pre5/vm-33.gz
It applies cleanly to both 2.4.19pre5 and 2.4.19pre6. Andrew splitted it
into orthogonal pieces for easy merging from Marcelo's side (modulo
-rest that is important too but that it's still quite monolithic, but
it's pointless to invest further effort at this time until we are
certain Marcelo will do its job and eventually merge it in mainline):
ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/patches/v2.4/2.4.19pre5/
So far a first part of those patches is been merged into mainline into
pre5 (not any previous kernel, if you've some problem reproducible with
pre4 pre3 pre2 and pre1 or any previous kernel that's not related to the
async flushing changes, I seen a bogus report floating around to Marcelo
about pre1 pointing to the vm changes, it can't be the vm changes if
it's pre[1234]).
This VM is under heavy stressing for weeks on my SMP highmem machine
with a real life DBMS workload in a real life setup with huge VM
pressure with mem=1024m and 1.2G of shm pushed in swap constantly by the
kernel, performance of the workload is now very good and exactly
reproducible and constant, so I recommend it for all production systems
(both lowmem desktops and highend servers).
Alternatively you can use the whole -aa patchkit, to get all the other
critical highend features like pte-highmem, highio etc...
I haven't bugreports pending on the vm patch.
Thanks,
Andrea
next prev parent reply other threads:[~2002-04-09 23:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 11:51 [2.4.17/18pre] VM and swap - it's really unusable Aviv Shavit
2002-02-26 0:09 ` Ken Brownfield
2002-02-26 4:40 ` Ken Brownfield
2002-04-09 20:45 ` Aviv Shavit
2002-04-09 21:16 ` Rik van Riel
2002-04-09 23:36 ` Andrea Arcangeli [this message]
2002-04-10 0:07 ` vm-33, strongly recommended [Re: [2.4.17/18pre] VM and swap - it's really unusable] Richard Gooch
2002-04-10 0:30 ` Andrea Arcangeli
2002-04-10 22:40 ` Richard Gooch
2002-04-10 23:51 ` Andrea Arcangeli
2002-04-10 8:55 ` Christoph Hellwig
2002-04-11 23:34 ` Ken Brownfield
2002-04-11 23:50 ` Aviv Shavit
2002-04-12 0:20 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2002-04-10 1:17 shane
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=20020410013609.A6875@dualathlon.random \
--to=andrea@suse.de \
--cc=avivshavit@yahoo.com \
--cc=brownfld@irridia.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