System, method and storage medium for providing fault detection and correction in a memory subsystem

[0001] This application is a continuation of U.S. patent application Ser. No. 10/977,914 filed Oct. 29, 2004, the contents of which are incorporated by reference herein in their entirety.

[0002] The invention relates to a memory subsystem and in particular, to providing fault detection and correction in a memory subsystem.

[0003] Computer memory subsystems have evolved over the years, but continue to retain many consistent attributes. Computer memory subsystems from the early 1980's, such as the one disclosed in U.S. Pat. No. 4,475,194 to LaVallee et al., of common assignment herewith, included a memory controller, a memory assembly (contemporarily called a basic storage module (BSM) by the inventors) with array devices, buffers, terminators and ancillary timing and control functions, as well as several point-to-point busses to permit each memory assembly to communicate with the memory controller via its own point-to-point address and data bus. FIG. 1 depicts an example of this early 1980 computer memory subsystem with two BSMs, a memory controller, a maintenance console, and point-to-point address and data busses connecting the BSMs and the memory controller.

[0004] FIG. 2, from U.S. Pat. No. 5,513,135 to Dell et al., of common assignment herewith, depicts an early synchronous memory module, which includes synchronous dynamic random access memories (DRAMs) 8, buffer devices 12, an optimized pinout, an interconnect and a capacitive decoupling method to facilitate operation. The patent also describes the use of clock re-drive on the module, using such devices as phase lock loops (PLLs).

[0005] FIG. 3, from U.S. Pat. No. 6,510,100 to Grundon et al., of common assignment herewith, depicts a simplified diagram and description of a memory system 10 that includes up to four registered dual inline memory modules (DIMMs) 40 on a traditional multi-drop stub bus channel. The subsystem includes a memory controller 20, an external clock buffer 30, registered DIMMs 40, an address bus 50, a control bus 60 and a data bus 70 with terminators 95 on the address bus 50 and data bus 70.

[0006] FIG. 4 depicts a 1990's memory subsystem which evolved from the structure in FIG. 1 and includes a memory controller 402, one or more high speed point-to-point channels 404, each connected to a bus-to-bus converter chip 406, and each having a synchronous memory interface 408 that enables connection to one or more registered DIMMs 410. In this implementation, the high speed, point-to-point channel 404 operated at twice the DRAM data rate, allowing the bus-to-bus converter chip 406 to operate one or two registered DIMM memory channels at the full DRAM data rate. Each registered DIMM included a PLL, registers, DRAMs, an electrically erasable programmable read-only memory (EEPROM) and terminators, in addition to other passive components.

[0007] As shown in FIG. 5, memory subsystems were often constructed with a memory controller connected either to a single memory module, or to two or more memory modules interconnected on a ‘stub’ bus. FIG. 5 is a simplified example of a multi-drop stub bus memory structure, similar to the one shown in FIG. 3. This structure offers a reasonable tradeoff between cost, performance, reliability and upgrade capability, but has inherent limits on the number of modules that may be attached to the stub bus. The limit on the number of modules that may be attached to the stub bus is directly related to the data rate of the information transferred over the bus. As data rates increase, the number and length of the stubs must be reduced to ensure robust memory operation. Increasing the speed of the bus generally results in a reduction in modules on the bus with the optimal electrical interface being one in which a single module is directly connected to a single controller, or a point-to-point interface with few, if any, stubs that will result in reflections and impedance discontinuities. As most memory modules are sixty-four or seventy-two bits in data width, this structure also requires a large number of pins to transfer address, command, and data. One hundred and twenty pins are identified in FIG. 5 as being a representative pincount.

[0008] FIG. 6, from U.S. Pat. No. 4,723,120 to Petty, of common assignment herewith, is related to the application of a daisy chain structure in a multipoint communication structure that would otherwise require multiple ports, each connected via point-to-point interfaces to separate devices. By adopting a daisy chain structure, the controlling station can be produced with fewer ports (or channels), and each device on the channel can utilize standard upstream and downstream protocols, independent of their location in the daisy chain structure.

[0009] FIG. 7 represents a daisy chained memory bus, implemented consistent with the teachings in U.S. Pat. No. 4,723,120. A memory controller 111 is connected to a memory bus 315, which further connects to a module 310a. The information on memory bus 315 is re-driven by the buffer on module 310a to a next module, 310b, which further re-drives the memory bus 315 to module positions denoted as 310n. Each module 310a includes a DRAM 311a and a buffer 320a. The memory bus 315 may be described as having a daisy chain structure with each bus being point-to-point in nature.

[0010] A variety of factors including faulty components and inadequate design tolerances may result in errors in the data being processed by a memory subsystem. Errors may also occur during data transmission due to “noise” in the communication channel (e.g., the bus 315). As a result of these errors, one or more bits, which may be represented as X, which are to be transmitted within the system, are corrupted so as to be received as “/X” (i.e., the logical complement of the value of X). In order to protect against such errors, the data bits may be coded via an error correcting code (ECC) in such a way that the errors may be detected and possibly corrected by special ECC logic circuits. A typical ECC implementation appends a number of check bits to each data word. The appended check bits are used by the ECC logic circuits to detect errors within the data word. By appending bits (e.g., parity bits) to the data word, each bit corresponding to a subset of data bits within the data word, the parity concepts may be expanded to provide the detection of multiple bit errors or to determine the location of single or multiple bit errors. Once a data bit error is located, a logic circuit may be utilized to correct the located erroneous bit, thereby providing single error correction (SEC). Many SEC codes have the ability to detect double errors and are thus termed SEC double error detecting (SEC-DED) codes.

[0011] FIG. 8 represents a typical parallel bus ECC structure that transfers a complete ECC word in a single cycle. The structure depicted in FIG. 8 is consistent with the teachings in U.S. Pat. No. 6,044,483 to Chen et al., of common assignment herewith. FIG. 8 depicts an 88/72 ECC for computer systems having an eight bit per chip memory configuration. The lines labeled “Wire 0” through “Wire 72” each represent a wire on the memory bus 315 with seventy-two wires. For a memory subsystem with an eight bit per chip memory configuration, sixty-four bits of data and eight ECC bits are transferred every cycle. The ECC word is transferred entirely in one cycle, and a SEC-DED code may be utilized to correct any single bit failure anywhere in the ECC word, including a hard wire or bitlane failure. In the case of a hard wire or bitlane failure, every transfer has the same bitlane in error with the ECC correcting it for each transfer.

[0012] FIG. 9 depicts a typical manner of defining symbol ECCs for use in fault detection and correction in a memory subsystem. FIG. 8 is consistent with the teachings of U.S. Pat. No. 6,044,483. As shown in FIG. 9, the symbols are four bits in length and the symbols are defined across bitlanes. As is known in the art, a symbol refers to a mathematical derivation of ECC and corresponds to a group of bits that the ECC is able to correct either individually or as a group. Referring to FIG. 9, assuming that data bits one through four are sourced from the same memory chip, respectively, data errors located by “symbol 1” can be localized to a particular memory chip (e.g., a DRAM).

[0013] Busses that are protected by ECC are typically run as single transfer busses with a SEC-DED code. In other words, any single bitlane failure is corrected by the SEC code because the ECC word is completely transmitted in one cycle (or shot or transfer). Thus, if a wire, contact, or bitlane is faulty, it would be a faulty bit in every transfer, and the SEC ECC will correct the error each cycle.

[0014] Defining symbols across bitlanes may be used to effectively isolate errors to memory chips when a relatively wide parallel ECC structure is implemented and a complete ECC word is transferred in a single cycle. However, defining symbols across bitlanes may not be effective in isolating errors to a particular memory chip or bus wire when a relatively narrow parallel interface is implemented with the ECC word (made up of data bits and ECC bits) being delivered in packets over multiple cycles.

[0015] Exemplary embodiments of the present invention include a memory subsystem with a memory bus and a memory assembly. The memory bus includes multiple bitlanes. The memory assembly is in communication with the memory bus and includes instructions (circuitry and/or software) for receiving an error code correction (ECC) word in multiple packets via the memory bus. The ECC word includes data bits and ECC bits arranged into multiple multi-bit ECC symbols. Each of the ECC symbols is associated with one of the bitlanes on the memory bus. The memory assembly also includes instructions for utilizing one of the ECC symbols to perform error detection and correction for the bits in the ECC word received via the bitlane associated with the ECC symbol.

[0016] Additional exemplary embodiments include a memory subsystem with a memory bus and a memory assembly. The memory bus includes multiple bitlanes. The memory assembly is in communication with the memory bus and includes instructions (circuitry and/or software) for creating an ECC word. The ECC word includes data bits and ECC bits arranged into multiple multi-bit ECC symbols. Each of the ECC symbols is associated with one of the bitlanes on the memory bus. The memory assembly also includes instructions for transmitting the ECC word in multiple packets via the memory bus.

[0017] Further exemplary embodiments include a method for providing error detection and correction. The method includes receiving an ECC word at a memory assembly in multiple packets via a memory bus. The ECC word includes data bits and ECC bits arranged into multiple ECC symbols. Each of the ECC symbols is associated with one bitlane on the memory bus. The method further includes utilizing one of the ECC symbols to perform error detection and correction to bits in the ECC word received via the bitlane associated with the symbol.

[0018] Still further exemplary embodiments include a storage medium encoded with machine readable computer program code for providing fault detection and correction in a memory subsystem. The storage medium includes instructions for causing a computer to implement a method. The method includes receiving an ECC word at a memory assembly in multiple packets via a memory bus. The ECC word includes data bits and ECC bits arranged into multiple ECC symbols. Each of the ECC symbols is associated with one bitlane on the memory bus. The method further includes utilizing one of the ECC symbols to perform error detection and correction to bits in the ECC word received via the bitlane associated with the symbol.

[0019] An additional exemplary embodiment of the present invention includes a communication system with a bus containing multiple bitlanes and a device in communication with the bus. The device includes instructions for receiving an ECC word in multiple packets via the bus. The ECC word includes data bits and ECC bits arranged into multiple multi-bit ECC symbols with each of the ECC symbols being associated with one of the bitlanes on the bus. One of the ECC symbols is utilized to perform error detection and correction for the bits in the ECC word received via the bitlane and associated with the ECC symbol. The number of ECC bits is greater than a second number of ECC bits in a SEC/DED implementation of equivalent bitlane dimension. In addition, the number of bitlanes utilized to transfer the ECC bits is less than a second number of bitlanes in an SEC/DED implementation of equivalent bitlane dimension.

[0037] Exemplary embodiments of the present invention utilize a symbol ECC interleaved such that the symbol orientation is along the bitlanes. A relatively narrow parallel interface is utilized with data that is delivered in packets over several transfers. Thus, the ECC word is two-dimensional in that the data bits and ECC bits are delivered in multiple cycles over a parallel interface. In order to provide protection for both random noise related soft errors on the bus, as well as systematic hard errors (errors such as a contact or wire failure along the bitlane), a new ECC scheme is employed. In addition, the capability of expanding the code to a higher order of robustness, for example going from a single symbol correcting code to a double symbol correcting code by using a spare wire(s), is available in this scheme. Exemplary embodiments of the present invention are contrasted against a detect/retry scheme where once an error is detected the data is re-sent. In exemplary embodiments of the present invention, errors are corrected on the fly, and in the event of a spare being deployed, the full ECC code is still available. Exemplary embodiments of the present invention provide an 88/72 ECC code that will detect all errors on a four bit symbol, correct all four bit symbol errors and detect all double four bit symbol errors (e.g., single 4-bit error correcting/double 4-bit error detecting (S4EC/D4ED).

SEC/DED=Single Error Correcting/Double Error Detecting

S4EC/D4ED=Single 4-bit Error Correcting/Double 4-bit Error Detecting

[0038] In an exemplary embodiment of the present invention, fault correction and detection is provided by a high speed and high reliability memory subsystem architecture and interconnect structure that includes single-ended point-to-point interconnections between any two subsystem components. The memory subsystem further includes a memory control function, one or more memory modules, one or more high speed busses operating at a four-to-one speed ratio relative to a DRAM data rate and a bus-to-bus converter chip on each of one or more cascaded modules to convert the high speed bus(ses) into the conventional double data rate (DDR) memory interface. The memory modules operate as slave devices to the memory controller, responding to commands in a deterministic manner, but do not self-initiate unplanned bus activity, except in cases where operational errors are reported in a real-time manner. Memory modules can be added to the cascaded bus with each module assigned an address to permit unique selection of each module on the cascaded bus. Exemplary embodiments of the present invention include a packetized multi-transfer interface which utilizes an innovative communication protocol to permit memory operation to occur on a reduced pincount, whereby address, command and data is transferred between the components on the cascaded bus over multiple cycles, and are reconstructed and errors corrected prior to being used by the intended recipient.

[0039] FIG. 10 depicts a cascaded memory structure that may be utilized by exemplary embodiments of the present invention when buffered memory modules 1006 (e.g., the buffer device is included within the memory module 1006) are in communication with a memory controller 1002. This memory structure includes the memory controller 1002 in communication with one or more memory modules 1006 via a high speed point-to-point bus 1004. Each bus 1004 in the exemplary embodiment depicted in FIG. 10 includes approximately fifty high speed wires for the transfer of address, command, data and clocks. By using point-to-point busses as described in the aforementioned prior art, it is possible to optimize the bus design to permit significantly increased data rates, as well as to reduce the bus pincount by transferring data over multiple cycles. Whereas FIG. 4 depicts a memory subsystem with a two to one ratio between the data rate on any one of the busses connecting the memory controller to one of the bus converters (e.g., to 1,066 Mb/s per pin) versus any one of the busses between the bus converter and one or more memory modules (e.g., to 533 Mb/s per pin), an exemplary embodiment of the present invention, as depicted in FIG. 10, provides a four to one bus speed ratio to maximize bus efficiency and minimize pincount.

[0040] Although point-to-point interconnects permit higher data rates, overall memory subsystem efficiency must be achieved by maintaining a reasonable number of memory modules 1006 and memory devices per channel (historically four memory modules with four to thirty-six chips per memory module, but as high as eight memory modules per channel and as few as one memory module per channel). Using a point-to-point bus necessitates a bus re-drive function on each memory module to permit memory modules to be cascaded such that each memory module is interconnected to other memory modules, as well as to the memory controller 1002.

[0041] FIG. 1 depicts a memory structure with cascaded memory modules and unidirectional busses that is utilized by exemplary embodiments of the present invention if all of the memory modules 1006 are buffered memory modules 1006. One of the functions provided by the memory modules 1006 in the cascade structure is a re-drive function to send signals on the memory bus to other memory modules 1006 or to the memory controller 1002. FIG. 11 includes the memory controller 1002 and four memory modules 1006a, 1006b, 1006c and 1006d, on each of two memory busses (a downstream memory bus 1104 and an upstream memory bus 1102), connected to the memory controller 1002 in either a direct or cascaded manner. Memory module 1006a is connected to the memory controller 1002 in a direct manner. Memory modules 1006b, 1006c and 1006d are connected to the memory controller 1002 in a cascaded manner.

[0042] An exemplary embodiment of the present invention includes two unidirectional busses between the memory controller 1002 and memory module 1006a (“DIMM #1”), as well as between each successive memory module 1006b-d (“DIMM #2”, “DIMM #3” and “DIMM #4”) in the cascaded memory structure. The downstream memory bus 1104 is comprised of twenty-two single-ended signals and a differential clock pair. The downstream memory bus 1104 is used to transfer address, control, data and error code correction (ECC) bits downstream from the memory controller 1002, over several clock cycles, to one or more of the memory modules 1006 installed on the cascaded memory channel. The upstream memory bus 1102 is comprised of twenty-three single-ended signals and a differential clock pair, and is used to transfer bus-level data and ECC bits upstream from the sourcing memory module 1006 to the memory controller 1002. Using this memory structure, and a four to one data rate multiplier between the DRAM data rate (e.g., 400 to 800 Mb/s per pin) and the unidirectional memory bus data rate (e.g., 1.6 to 3.2 Gb/s per pin), the memory controller 1002 signal pincount, per memory channel, is reduced from approximately one hundred and twenty pins to about fifty pins.

[0043] FIG. 12 depicts a buffered module wiring system that is utilized by exemplary embodiments of the present invention. FIG. 12 is a pictorial representation of a memory module with shaded arrows representing the primary signal flows. The signal flows include the upstream memory bus 1102, the downstream memory bus 1104, memory device address and command busses 1210 and 1206, and memory device data busses 1204 and 1208. In an exemplary embodiment of the present invention, a buffer device 1202, also referred to as a memory interface chip provides two copies of the address and command signals to the synchronous DRAMs (SDRAMs) 1204 with the right memory device address and command bus 1206 exiting from the right side of the buffer device 1202 for the SDRAMs 1204 located to the right side and behind the buffer device 1202 on the right. The left memory device address and command bus 1210 exits from the left side of the buffer device 1202 and connects to the SDRAMs 1204 to the left side and behind the buffer device 1202 on the left. Similarly, the data bits intended for SDRAMs 1204 to the right of the buffer device 1202 exit from the right of the buffer module 1202 on a right memory device data bus 1208. The data bits intended for the left side of the buffer device 1202 exit from the left of the buffer device 1202 on the left memory device data bus 1204. The high speed upstream memory bus 1102 and downstream memory bus 1104 exit from the lower portion of the buffer device 1202, and connect to a memory controller or other memory modules either upstream or downstream of this memory module 1006, depending on the application. The buffer device 1202 receives signals that are four times the memory module data rate and converts them into signals at the memory module data rate.

[0044] FIG. 13 depicts a downstream frame format that is utilized by exemplary embodiments of the present invention to transfer information downstream from the memory controller 1002 to the memory modules 1006. In an exemplary embodiment of the present invention, the downstream frame consists of eight transfers with each transfer including twenty-two signals and a differential clock (twenty-four wires total). The frame further consists of eight command wires (c0 through c7) 1308, nine data wires (di0 through di8) 1306, four bus error correction code (ECC) wires (ecc0 through ecc3) 1304 and a spare wire (spare) 1302. The seventy-two data bits are shown in FIG. 13 as bits di0 through di8, and consist of nine wires with eight transfers on each wire for each frame. In exemplary embodiments of the present invention, the frame format depicted in FIG. 13 may be utilized to deliver one or two memory commands plus seventy-two bits of write data per memory clock cycle. The numbering of each data bit, as well as for other bits, is based on the wire used, as well as the specific transfer. D34 refers to data bit 3 (of bits 0 through 8) and transfer 4 (of transfer 0 through 7). The command bit field is shown as c0 through c7, and consists of sixty-four bits of information provided to the module over eight transfers.

[0045] The ECC bit field (ecc0 through ecc3) consists of thirty-two bit positions over eight transfers but is actually formatted in groups of sixteen bits. Each sixteen bit packet consists of four transfers over each of the four wires and provides the bus level fault detection and correction across each group of four bus transfers. The bus level error correcting code fault detection and correction is performed by a logic block that includes instructions to carry out the detection and correction. The spare bit position may be used to logically replace any of the twenty-one wires, also defined as bitlanes, used to transfer bits in the command, data and ECC fields should a failure occur in one of the bitlanes that results in exceeding a system-assigned failure threshold limit. The spare wire may be utilized to replace a failing segment between any two directly connected assemblies (i.e., between the memory controller 1002 and the memory module 1006a, or between any two memory modules 1006a-d), to replace a wire due to events, such as a wire failure, a connector failure, a solder interconnect failure, a driver failure and/or a receiver failure. Out of the one hundred and seventy-six possible bit positions, one hundred and sixty-eight are available for the transfer of information to the memory module 1006, and of those one hundred and sixty-eight bit positions, thirty-two bit positions are further assigned to providing ECC protection on the bus transfers themselves, thereby allowing a total of one hundred and thirty-six bit positions to be used for the transfer of information to the memory module 1006. The frame format depicted in FIG. 13 is applicable to incoming signals to the memory module 1006 from the direction of the memory controller, as well as the outgoing signals to any downstream memory modules 1006.

[0046] FIG. 14 depicts an upstream frame format that is utilized by exemplary embodiments of the present invention to transfer information upstream from the memory module 1006 to either the memory controller 1002 or an upstream memory module 1006. In an exemplary embodiment of the present invention, the upstream frame consists of eight transfers with each transfer including twenty-three signals and a differential clock (twenty-five wires total). The frame further consists of eighteen data wires (do0 through do17) 1406, four bus ECC wires (ecc0 through ecc3) 1404 and a spare wire (spare) 1402. In exemplary embodiments of the present invention, the frame format depicted in FIG. 14 may be utilized to deliver one hundred and forty-four read data bits per memory clock cycle. The numbering of each data bit, as well as for other bits, is based on the wire used, as well as the specific transfer. D34 refers to data bit 3 (of bits 0 through 17) and transfer 4 (of transfer 0 through 7).

[0047] The ECC bit field (ecc0 through ecc3) consists of thirty-two bit positions over eight transfers but is actually formatted in groups of sixteen bits. Each sixteen bit packet consists of four transfers over each of the four wires with error correction being performed every four transfers. The spare wire position may be used to logically replace any of the twenty-two wires used to transfer bits in the data and ECC fields should a failure occur in one of these wires that is consistent in nature. A failure may be considered to be consistent in nature if it exceeds a system dependent threshold value (e.g., number of times the failure is detected). Single bitlane failures may be corrected on the fly by the bus level ECC, while a system service element, such as a service processor, may decide to spare out a failing segment to repair hard (e.g., periodic, repeating and continuous) failures that may occur during system operation.

[0048] FIG. 15 is a table with symbols defined across bitlanes, using the upstream frame format depicted in FIG. 14 as an example. Each column 1506 represents the bits of a symbol (i.e., “bit 1”, “bit 2”, “bit 3”, and “bit 4”). Each row represents a symbol (i.e., “symbol 1”, “symbol 2”, etc.). Bit 1 of symbol 1 contains data bit D00 from FIG. 14, bit 2 of symbol 1 contains data bit D10 from FIG. 14, bit 3 contains data bit D20 from FIG. 14 and bit 4 contains data bit D30 from FIG. 14. All of the data bits contained in symbol 1 are transferred during the first transfer within the frame, or transfer 0. As described previously, the ECC is checked for every four transfers in a frame, or for every half frame. The ECC word, including eighty-eight bits (the spare bitlane is included in place of a failing bitlane only if it is being utilized), is transferred over multiple cycles (e.g., four) such that a hard fail in any bitlane or wire will result in a multiple-bit error. A typical single symbol correcting/double symbol detecting (SSC/DSD) ECC scheme will not be effective in correcting hard bitlane failures for the symbol scheme depicted in FIG. 15 because the bits within the symbol are not being sent on the same bitlane. Also, a SSC/DSD code would not be effective either because symbols are generally distributed among adjacent bits of a bus. This approach to forming symbols across bitlanes, as applied to the upstream format shown in FIG. 14, is shown in FIG. 15.

[0049] FIG. 16 is a table with symbols defined along the bitlanes, in accordance with exemplary embodiments of the present invention, using the upstream frame format depicted in FIG. 14 as an example. The first four columns 1604 in FIG. 16 represent the bits of a symbol (i.e., “bit 1”, “bit 2”, “bit 3”, and “bit 4”). The last column 1606 contains the bitlane being covered by the symbol. Each row represents a symbol (i.e., “symbol 1”, “symbol 2”, etc.). Bit 1 of symbol 1 contains data bit D00 from FIG. 14, bit 2 of symbol 1 contains data bit D01 from FIG. 14, bit 3 contains data bit D02 from FIG. 14 and bit 4 contains data bit D03 from FIG. 14. Symbol 1 covers bitlane 5 in FIG. 14. Bit 1 was transferred during transfer zero, bit 2 during transfer one, bit 3 during transfer two and bit 4 during transfer three. Interleaving the data bits in the ECC code such that the ECC symbol is defined along the bitlanes allows the data bits to be protected along the bitlane dimension rather than in the databit dimension depicted in FIG. 15. Again, the ECC is checked every four transfers in a frame, or for every half frame. The ECC word, including eighty-eight bits (the spare bitlane is included in place of a failing bitlane only if it is being utilized), is transferred over multiple cycles (e.g., four). The ECC word includes both data bits and ECC bits. Data bits may include, but are not limited to, command bits, write data bits and read data bits. In addition, ECC bits may be treated as data bits with the ECC processing described herein being applied to the ECC bits. Thus, in an exemplary embodiment, the ECC bits may also be data bits.

[0050] The symbols in FIG. 16 are defined to span a single bitlane, and if any of the hardware that is associated with any of the bitlanes fails, the failure will affect all four of the data bits that are transferred via the failing bitlane. Orienting the symbol along the bitlanes allows a single and/or multiple errors caused by a failing bitlane to be detected and corrected.

[0051] A further advantage of defining symbols along bitlanes is that it uncouples the requirement to have unique data/address/command format with the ECC word. Exemplary embodiments of the present invention allow data bits one through seventy-two to be any combination of data, address or command information.

[0052] Another benefit to defining symbols along bitlanes is that it is flexible and modular in that an additional bitlane can be added to the bus for the purposes of additional data, additional robustness, or even as a spare. Because the additional bitlane is dedicated to the added function, no further structural changes are required to allow the benefits of the added wire to accrue (either in more data capacity, spare capability, or a more robust ECC).

[0053] In addition, the scheme of defining symbols along bitlanes can be expanded to include an arbitrary number of transfers. This will cause the ECC symbol size to commensurately grow, but conceptually and structurally, this idea can be extended in the transfer dimension without any loss of coverage.

[0054] In general, the narrower the bus, the greater percentage of signals that must be checkbits to provide the same level of protection. For classic Hamming codes, or traditional SEC/DED bus ECC, the following table illustrates this point:

[0055]

Maximum Data Signals	Checkbit Signals	Percent Overhead
4	4	50%
11	5	31%
26	6	19%
57	7	11%
120	8	6%
247	9	4%

This can be compared to exemplary embodiments of the present invention including symbol oriented bus ECC where 4 checkbits are utilized for up to 253 data signals with a resulting overhead of 1.6%. Therefore, six checkbits could have been utilized to support 17 or 18 databits if the traditional SEC/DED had been utilized.

[0056] One drawback to using the traditional SEC/DED for read and write data busses that are daisy-chained through the support ASIC is that each additional checkbit gets multiplied by four in terms of ASIC pincount (i.e., 2 additional checkbits for each bus equals 8 additional ASIC pins). Another drawback to using the traditional SEC/DED is that the probability that a code will detect random, multibit errors is inversely proportional to the expression “2 raised to the nth power”, where n is the number of checkbits. This means that a (24,18) SEC/DED code with 6 checkbits has a figure of merit of 1/(2⁶)=0.016. This is contrasted to exemplary embodiments of the present invention described herein that have a figure of merit of 1/(2¹⁶)=0.000015, which is about 100 times better. A further advantage of exemplary embodiments of the present invention over the traditional SEC/DED approach is that the current design point described herein of 18 data bitlanes can be expanded to support up to 253 bitlanes without adding new checkbits. In contrast, the traditional SEC/DED approach would require the addition of checkbits such that even adding 9 additional data bitlanes (for a total of 27) would require an additional checkbit.

[0057] As described above, the embodiments of the invention may be embodied in the form of computer-implemented processes and apparatuses for practicing those processes. Embodiments of the invention may also be embodied in the form of computer program code containing instructions embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other computer-readable storage medium, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention. The present invention can also be embodied in the form of computer program code, for example, whether stored in a storage medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention. When implemented on a general-purpose microprocessor, the computer program code segments configure the microprocessor to create specific logic circuits.

[0058] While the invention has been described with reference to exemplary embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiment disclosed as the best mode contemplated for carrying out this invention, but that the invention will include all embodiments falling within the scope of the appended claims. Moreover, the use of the terms first, second, etc. do not denote any order or importance, but rather the terms first, second, etc. are used to distinguish one element from another.