From: rwhron@earthlink.net
To: gyro@zeta-soft.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Performance issue on dual Athlon MP
Date: Wed, 6 Mar 2002 17:09:51 -0500 [thread overview]
Message-ID: <20020306170951.A31564@rushmore> (raw)
> I have a dual Athlon MP box (Tyan S2460 Tiger MP, 1.53 GHz, 2.5 GB Corsair
> PC2100). The initial installation was of SuSE 7.3, but I have upgraded to
> 2.4.17 with Andrea's 3.5 GB userspace patch.
> Is this a known problem with 2.4.17 and/or the 3.5 GB userspace patch? I
> have not tried turning off the 3.5 GB config option (`CONFIG_05GB'). I do
> have `CONFIG_MK7' set.
The configuration I would try first on 2.4.19pre1aa1 with 2.5 GB of RAM is
CONFIG_3GB=y and CONFIG_NOHIGHMEM=y. If that causes some other problem,
I'd go with CONFIG_2GB, then finally CONFIG_1GB. Each config changes
the user/kernel memory split. The loads I've run suggest for best
performance:
CONFIG_2GB > CONFIG_1GB > CONFIG_05GB
On my 1GB box, I've been running CONFIG_2GB for a couple months and
performance is great. Only lingering question for me is the handling
of oom. Oom hasn't caused be a problem, but I haven't seen the oom
killer do it's work when I create an oom condition.
BTW, Andrew Morton's read_latency2 patch is a winner. The read_latency2
diff I use on my 2.4.19pre1aa1 boxes is at:
http://home.earthlink.net/~rwhron/kernel/read_latency2-2.4.19pre1aa1.diff
--
Randy Hron
next reply other threads:[~2002-03-06 22:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 22:09 rwhron [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-06 19:28 Performance issue on dual Athlon MP Dieter Nützel
2002-03-06 20:49 ` John Jasen
2002-03-07 23:20 ` Scott L. Burson
2002-03-07 23:44 ` Alan Cox
2002-03-08 0:24 ` Randy.Dunlap
2002-03-11 9:32 ` Jens Axboe
2002-03-11 20:13 ` Randy.Dunlap
2002-03-14 15:49 ` Scott L. Burson
2002-03-06 18:47 Scott L. Burson
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=20020306170951.A31564@rushmore \
--to=rwhron@earthlink.net \
--cc=gyro@zeta-soft.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