From: Nils Holland <nils@nightcastleproductions.org>
To: Peter Rasmussen <plr@udgaard.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug in chipset or feature in kernel?
Date: Thu, 24 May 2001 11:09:44 +0200 [thread overview]
Message-ID: <200105240909.f4O99ie01182@collie.ncptiddische.net> (raw)
In-Reply-To: <200105240726.JAA00325@udgaard.com>
In-Reply-To: <200105240726.JAA00325@udgaard.com>
On Thursday 24 May 2001 09:26, Peter Rasmussen wrote:
> Is the below described problem a problem with my chipset, the memory
> subsystem in the kernel, a combination of those or something entirely
> different?
>
> Is there any test I should perform to investigate further eg. to find a
> workaround for a chipset limitation, if that is the problem? It looks as if
> there is a tuning for max. performance around 128MB. Coincidence?
I'm not sure about this as I have never had to deal with something like that
myself. However, I think that when adding more RAM, you should also add more
Cache to your system - otherwise performance may drop as described by you.
Don't ask me, though, how one is supposed to add more cache to a mainboard...
If my above assumption is not right, I hope that someone will share the
actual facts with you and me ;-)
Greetings
Nils
--
----------------------------------------------------------
Nils Holland - nils@nightcastleproductions.org
NightCastle Productions - Linux in Tiddische, Germany
http://www.nightcastleproductions.org
"They asked me where this earthquake would begin,
I offered to let them feel my pulse."
----------------------------------------------------------
prev parent reply other threads:[~2001-05-24 9:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 7:26 Peter Rasmussen
2001-05-24 9:09 ` Nils Holland [this message]
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=200105240909.f4O99ie01182@collie.ncptiddische.net \
--to=nils@nightcastleproductions.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plr@udgaard.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
all inboxes | Powered by JetHome®