From: Patrick Chase <pchase2@pacbell.net>
To: linux-kernel@vger.kernel.org, g.vanderzouw@chello.nl
Subject: Re: Status of the VIA KT133a and 2.4.x debacle?
Date: Sun, 02 Sep 2001 21:58:21 -0700 [thread overview]
Message-ID: <999493106.15509.33.camel@homebase.localdomain> (raw)
Gerbrand van der Zouw wrote:
> I have a MSI K7T Turbo board with Athlon 1.2 GHz. Recently I
> upgraded my Award Bios from 2.7 to 2.9. This new version has
> "memory bank interleaving". It also improves the stability of
> my system a lot. I do not know if these are related, but is
> may be a hint for some of the experts out there.
Are you enabling or disabling bank interleaving with the new BIOS?
I would say that given the nature of the prefetch optimizations
which appear to be causing instabilities, problems related to
SDRAM bank interleaving of lack thereof should be near the top
of any list of suspects.
Very briefly, SDRAM parts have multiple banks (either 2 or 4
depending on capacity). Bank select lines are used to control
which bank is active for a given access cycle. The existence
of the banks is significant for two reasons:
1. Each bank can have a separate page (~= row address)
open. If you're alternating accesses between two separate address
ranges, then performance may be higher if they're in separate
banks, as this could potentially avoid a lot of page openings.
2. Unselected banks can process previously issued multi-
cycle commands while the selected bank is returning data. For
example, you could request a new address from one bank, and
then transfer previously requested data from another bank during
the first bank's CAS latency.
The "native" address layout of SDRAM devices has each bank a
contiguous region (i.e. no interleave). An SDRAM controller may
instead cause the banks to appear interleaved to the processor
by simply remapping a few address bits. The "interleave" option
in your BIOS enables exactly such a remapping in the north
bridge's SDRAM controller.
Here's why the Athlon prefetch optimization could potentially
interact with the interleave setting: The entire point of
prefetching is to cause consecutive cache lines to be fetched
with as much overlap as possible (i.e. the next line is
requested before the current one has been read in). When
this is done with interleave enabled, the result is consecutive
accesses to alternating pages, in which case the chipset will
be able to exploit overlap as described in (2) above to hide
latencies. I can come up with rationales for why this could either
cause instability or help it, though I think I'll leave that to
those who knows more than I.
-- Patrick Chase
next reply other threads:[~2001-09-03 4:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-03 4:58 Patrick Chase [this message]
2001-09-04 22:14 ` Gerbrand van der Zouw
-- strict thread matches above, loose matches on Subject: below --
2001-09-01 14:19 Simen Thoresen
2001-09-01 17:05 ` Simen Thoresen
2001-09-01 17:11 ` Nicholas Knight
2001-09-02 22:53 ` Gerbrand van der Zouw
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=999493106.15509.33.camel@homebase.localdomain \
--to=pchase2@pacbell.net \
--cc=g.vanderzouw@chello.nl \
--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
all inboxes | Powered by JetHome®