From: Luca Montecchiani <m.luca@iname.com>
To: Robert Love <rml@tech9.net>
Cc: Richard Gooch <rgooch@ras.ucalgary.ca>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [FAQ?] More ram=less performance (maximum cacheable RAM)
Date: Wed, 22 Aug 2001 08:27:31 +0200 [thread overview]
Message-ID: <3B8350D3.CDE749E1@iname.com> (raw)
In-Reply-To: <3B82B988.50DE308A@iname.com> <200108211957.f7LJvEt20846@vindaloo.ras.ucalgary.ca> <998430817.3139.41.camel@phantasy>
Robert Love wrote:
>
> 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.
ciao,
luca
--
------------------------------------------------------------------
E-mail......: Luca Montecchiani <m.luca@iname.com>
W.W.W.......: http://i.am/m.luca - http://luca.myip.org
Speakfreely.: sflwl -hlwl.fourmilab.ch luca@
I.C.Q.......: 17655604
-----------------------=(Linux since 1995)=-----------------------
Non esiste vento favorevole per il marinaio che non sa dove andare
Seneca
next prev parent reply other threads:[~2001-08-22 6:28 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 [this message]
2001-08-22 11:12 ` Wakko Warner
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=3B8350D3.CDE749E1@iname.com \
--to=m.luca@iname.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
--cc=rml@tech9.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.