From: Wakko Warner <wakko@animx.eu.org>
To: Luca Montecchiani <m.luca@iname.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [FAQ?] More ram=less performance (maximum cacheable RAM)
Date: Wed, 22 Aug 2001 07:12:13 -0400 [thread overview]
Message-ID: <20010822071213.A9273@animx.eu.org> (raw)
In-Reply-To: <3B82B988.50DE308A@iname.com> <200108211957.f7LJvEt20846@vindaloo.ras.ucalgary.ca> <998430817.3139.41.camel@phantasy> <3B8350D3.CDE749E1@iname.com>
In-Reply-To: <3B8350D3.CDE749E1@iname.com>; from Luca Montecchiani on Wed, Aug 22, 2001 at 08:27:31AM +0200
> >
> > It also has nothing to do with Linux. Some motherboard's TAG RAM do not
> > allow for caching more than xMB.
>
> I'm just proposing to update the FAQ to help people like me
> that thinking to gain speed doubling the system ram have seen
> a severe performance drop for certain task like compiling the
> kernel .
>
> Answer :
> It has nothing to do with Linux, maybe your motherboard's TAG Ram
> do not allow for caching more than xMB.
The bios has something to do with that as well. I have a dual pentium
machine at work that was really slow. I looked in the bios and it has an
option to cache 64mb or 512mb. speed up my kernel compiles (2.2.x) by about
12 minutes. (took 20, after the change, it took about 8)
--
Lab tests show that use of micro$oft causes cancer in lab animals
next prev parent reply other threads:[~2001-08-22 11:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 19:42 [FAQ?] More ram=less performance (maximum cacheable RAM) Luca Montecchiani
2001-08-21 19:57 ` Richard Gooch
2001-08-21 20:38 ` Luca Montecchiani
2001-08-21 21:53 ` Robert Love
2001-08-22 6:27 ` Luca Montecchiani
2001-08-22 11:12 ` Wakko Warner [this message]
2001-08-22 21:26 ` idalton
2001-08-23 5:19 ` Richard Gooch
2001-08-23 11:35 ` Luca Montecchiani
2001-08-28 14:23 ` Holger Lubitz
-- strict thread matches above, loose matches on Subject: below --
2001-08-21 22:01 Samium Gromoff
2001-08-22 9:49 Samium Gromoff
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=20010822071213.A9273@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.luca@iname.com \
/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