PROVIDING A VARIABLE FRAME FORMAT PROTOCOL IN A CASCADE INTERCONNECTED MEMORY SYSTEM

• US 20100005212A1
• Filed: 07/01/2008
• Published: 01/07/2010
• Est. Priority Date: 07/01/2008
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Gower, Kevin C., Maule, Warren E., Trombley, Michael R., Van Huben, Gary A.
• Application Number:
  US12/166,244
• Publication Number:
  US 20100005212A1
• Time in Patent Office: Days
• US Class Current: 710/308
• CPC Class Codes: G06F 13/4234 being a memory bus

Abstract

Systems and methods for providing a variable frame format protocol in a cascade interconnected memory system. The systems include a memory hub device that utilizes a first bus interface to communicate on a high-speed bus. The hub device also includes frame decode logic for translating variable format frames received via the first bus interface into memory device commands and data. The translating includes identifying write data headers and associated write data for self-registering write to data buffer commands.

Claims

1. A memory hub device comprising:

a first bus interface for communicating with a high-speed bus; and

frame decode logic for translating variable format frames received via the first bus interface into memory device commands and data, the translating including identifying write data headers and associated write data for self-registering write to data buffer commands.

2. The memory hub device of claim 1 wherein the frames include write data bits and the identifying includes:

determining placement of write data bits in the frames;

monitoring contents of the write data bits;

identifying a write data header for a self-registering write to data buffer command in the write data bits, the write data header specifying a length of associated write data; and

identifying the associated write data in the write data bits, the identifying responsive to the write data header.

3. The memory hub device of claim 2 wherein the frame includes a frame type field and the determining placement is responsive to the frame type field.

4. The memory hub device of claim 2 wherein the frames include write data bits and associated write data for a self-registering write to data buffer command is located in write data bits that immediately follow the write data header for the self-registering write data to buffer command.

5. The memory hub device of claim 2 wherein the length of the write data header is one byte.

6. The memory hub device of claim 2 wherein the length of the associated write data is thirty-six bytes.

7. The memory hub device of claim 2 wherein the length of the associated write data is seventy-two bytes.

8. The memory hub device of claim 1 wherein each frame includes two or more blocks and one or both of a write data header and associated write data for at least one of the self-registering write to data buffer commands span at least two blocks.

9. The memory hub device of claim 1 wherein one or both of a write data header and associated write data for at least one of the self-registering write to data buffer commands span at least two or more frames.

10. The memory hub device of claim 1 further comprising a plurality of write data buffers, wherein the write data headers include target hub device identifiers, and the hub device writes associated write data for a self-registering write to data buffer command to one of the write data buffers in response to the hub device being identified as the target hub device.

11. The memory hub device of claim 1 further comprising a plurality of write data buffers, wherein the write data headers include target hub device identifiers and target write data buffer identifiers, and the hub device writes associated write data for a self-registering write to data buffer command to one of the write data buffers in response to the hub device being identified as the target hub device and to the write data buffer being identified as the target write data buffer.

12. The memory hub device of claim 1 wherein the variable format frames include CRC bits, frame type indicator bits, and one of write data bits, write data bits and one command, and write data bits and two commands based on contents of the frame type indicator bits.

13. The memory hub device of claim 1 wherein the high-speed bus includes a plurality of wires, each wire capable of carrying both data and commands.

14. A method for providing a variable frame format protocol in a cascade interconnected memory system, the method comprising:

receiving frames of varying formats on a high-speed bus, the receiving at a hub device in a cascade interconnected memory system, each frame including a frame type indicator and one or more write data bits;

determining placement of the write data bits in the frames, the determining responsive to the frame type indicator;

monitoring contents of the write data bits;

identifying a write data header for a self-registering write to data buffer command in the write data bits, the write data header specifying a length of associated write data and a target hub device identifier;

identifying the associated write data in the write data bits, the identifying responsive to the write data header; and

writing the associated write data to a write data buffer at the hub device in response to the hub device being identified as the target hub device.

15. The method of claim 14 wherein the associated write data is located in write data bits that immediately follow the write data header.

16. The method of claim 14 wherein each frame includes two or more blocks and one or both of the write data header and the associated write data for the self-registering write to data buffer command span at least one of two or more blocks and two or more frames.

17. A memory controller comprising:

a first bus interface for communicating with one or more hub devices in a cascade interconnect memory system via a high-speed bus; and

frame encoding logic for generating variable format frames for transmission to the hub devices, the generated frames comprising;

frame type indicators for specifying locations of write data bits in the frames; and

write data headers and associated write data for self-registering write to data buffer commands, the write data header and associated write located in the write data bits.

18. The memory controller of claim 17 wherein each frame includes two or more blocks and one or both of a write data header and associated write data for at least one of the self-registering write to data buffer commands span at least two blocks.

19. The memory controller of claim 17 wherein one or both of a write data header and associated write data for at least one of the self-registering write to data buffer commands span at least two or more frames.

20. A design structure tangibly embodied in a machine readable medium for designing, manufacturing, or testing an integrated circuit, the design structure comprising:

a first bus interface for communicating with a high-speed bus; and

frame decode logic for translating variable format frames received via the first bus interface into memory device commands and data, the translating including identifying write data headers and associated write data for self-registering write to data buffer commands.