Navigate:

Advice
Beginners
BIOS Guide
CPUs
Links
Mainboards
Memory
Network
Storage
Video/Sound Cards

Contact
Forum
SiteMap
Sponsors
WebNews
Home
. .

Prices:
CPU
Intel
P4 2.4C-800
P4 2.6C-800
P4 2.8C-800
P4 3.0-800
P4 3.2-800

AMD
AthlonXP
XP 1700+
XP 2000+
XP 2400+
XP 2500+
XP 2700+
XP 3000+
XP 3200+

Athlon64
Athlon64 3200+
Athlon64 FX-51

Opteron
Opteron 240
Opteron 242
Opteron 244
Opteron 246

Memory

Corsair
Crucial
Kingston
Mushkin
OCZ

Search Prices:








































































LOSTCIRCUITS

SHORTCUTS:
Top
Brookdale Chipset in Depth
VIA P4X266
ASUS P4B
MSI 845Pro2-R
Intel D850MD
Shuttle AV40
Test Configurations, Glitches
Stream
SiSoft Sandra
Expendable, Aquamark
Quake3 Arena
CAD, Video Editing
Confusion and Disillusion
 P4 2.0 GHz Platform Production Boards   
i845, i850, VIA P4X266
(Review by MS, 9/2001)

Brookdale in Detail

In general, the chipset follows the traditional Intel Hub architecture with a memory controller hub (MCH) connected to the I/O controller hub (ICH) via a 266MB/sec high speed interface to warrant enough bandwidth to satisfy simultaneous access of 2 IDE channels and concomitant PCI or other daughter device usage


Summary Diagram of the Intel i845 "Brookdale" SDRAM chipset. Breaking the memory limitations of the i815 chipset, Brookdale supports up to 3 x 1 GB unbuffered non-registered DIMMs. Registered DIMMs are not supported by the chipset, putting an effective limitation of 7698 MB system memory in place at the current state of SDRAM technology. A 266 MB/sec Hub interconnect bandwidth doubles the possible throughput of the older PCI bus which is now a branch-off of theI/O controller hub ICH.

Regardless of whether one likes Intel or not, the technology has always been at the very forefront. Therefore, it isn't any surprise either that the new Brookdale chipset does not feature just the average garden variety SDRAM controller but, in fact, goes a few extra miles.

The two most interesting features of the new memory controller are somewhat related, that is, the controller uses the open page policy already known from the i815 chipset with the option of leaving the pages open indefinitely. In contrast to the i815 MCH, however, the i845 MCH allows simultaneous keeping open of as much as 24 pages, thereby increasing the probability of a request coming back to the same page at some point. Keep in mind that the 24 open pages are a blanco statement for the entire memory architecture, that is 3 DIMM slots with 2 physical banks each or, to rephrase it, each bank can only keep 4 pages open at the time. Thus, while in theory, 24 open pages look very appealing, in practice, one needs to consider that:

Therefore, 24 open pages are only possible with all banks populated. This results in 12288 pages total and, therefore, the probability of a memory request falling into the same page is relatively low. On the other hand, the locality of data (coherent data are written to coherent blocks of memory in the same pages) and the not truly random accesses in many desktop applications increase the probability of page hits quite substantially.

The drawback of keeping a page open over an extended period of time, however, is that a page miss will cause additional penalty cycles because the open pages need to be closed first before even a bank activate command can be issued which opens a new page. Aside from that, there are further temporal considerations, since every page will expire after a certain time, simply because the operations of the system have moved on. An additional problem is found in the form of the necessary refresh cycles. Since DRAM cells lose the data because of leakage currents, each cell's content needs to be refreshed within certain intervals. The protocol used by the i845 controller is the old CAS-before-RAS (CBR), that is a complete read cycle is executed for each row, meaning, the data are read out into the sense amplifiers and then restored to the cell of origin after satisfying the RAS pulse width. There are different ways though, by which the scheduling of a refresh can be accomplished. The easiest possibility is to just move up or down the row decoder in ascending or descending order and have each row do its thing. A different approach is to use a refresh queue and do a burst refresh of several rows at a time. Intel is using yet a different approach called flexible memory refresh, meaning, there is a dynamic scheduling by means of which the refresh of open pages can be postponed if there is a probability that the data might still be requested.

Those scheduling issues aside, open pages are no good if there are no chipset buffers that can hold the data. Intel took care of this issue by adding a 12 level deep in order queue (IOQ) so that data from different open pages can be read consecutively into the pipeline. What it comes down to is the possibility of funneling 12 consecutive 64 bit reads to the CPU.

Internally, the amount of data needs to be made accessible to the CPU using the quad pumped FSB with its virtual 400 MHz operating frequency and the easy way to accomplish it is to increase bandwidth four-fold by means of widening the data path to 256 bit (internally). Other features of the chipset are old acquaintances like the write buffer. Only 5% of the entire memory traffic are writes, however, a single bit write can interrupt a burst read and, thus, it is much better to collect these individual writes and write them whenever there is a gap in the read sequence.

next page:    => Brookdale continued =>

Click Here!

If you enjoyed reading this article and found it useful, please consider making a small donation to LostCircuits.
Thank you!

General disclaimer: This page only reflects the author's personal opinion and assumes no responsibility whatsoever regarding any of the contents or any damages that may occur explicitly or implicitly from reading the contents of this site. All names and trademarks mentioned in this review are the exclusive property of the respective parent companies.
All contents of this site are protected by international copyright laws. Reproduction of the contents even in parts is not allowed