US20010044885A1 - Processing memory requests that target memory banks - Google Patents
Processing memory requests that target memory banks Download PDFInfo
- Publication number
- US20010044885A1 US20010044885A1 US09/898,277 US89827701A US2001044885A1 US 20010044885 A1 US20010044885 A1 US 20010044885A1 US 89827701 A US89827701 A US 89827701A US 2001044885 A1 US2001044885 A1 US 2001044885A1
- Authority
- US
- United States
- Prior art keywords
- bank
- memory
- pending operation
- idle
- conflicts
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 230000015654 memory Effects 0.000 title claims abstract description 107
- 238000000034 method Methods 0.000 claims description 7
- 238000010586 diagram Methods 0.000 description 5
- 230000001360 synchronised effect Effects 0.000 description 4
- 239000000872 buffer Substances 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 229910003460 diamond Inorganic materials 0.000 description 2
- 239000010432 diamond Substances 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/14—Handling requests for interconnection or transfer
- G06F13/16—Handling requests for interconnection or transfer for access to memory bus
- G06F13/1605—Handling requests for interconnection or transfer for access to memory bus based on arbitration
- G06F13/1647—Handling requests for interconnection or transfer for access to memory bus based on arbitration with interleaved bank access
Definitions
- the invention relates to processing memory requests that target memory banks.
- synchronous RAMs such as synchronous dynamic random access memories (SDRAMs), SyncLink dynamic random access memories (SLDRAMs), Rambus dynamic random access memories (RDRAMs) and double data rate (DDR) SDRAM memories.
- SDRAMs synchronous dynamic random access memories
- SLDRAMs SyncLink dynamic random access memories
- RDRAMs Rambus dynamic random access memories
- DDR double data rate SDRAM memories.
- the SyncLink standard has been assigned the tentative designation of IEEE-1596.7 by the Microprocessor & Microcomputer Standards Committee (MMSC) of the Institute of Electrical and Electronics Engineers (IEEE).
- MMSC Microprocessor & Microcomputer Standards Committee
- the Rambus® standard is published by Rambus, Incorporated of Mountain View, Calif.
- synchronous RAM may generally be organized into memory banks 12 , as depicted in FIG. 1.
- Banks represent a physical compartmentalization of memory space, where each bank may correspond to a unit or array of physical memory.
- a bank may be further divided into pages, where a page is typically defined in terms of a row address. All those memory locations in a bank having a common row address are said to be on the same page of memory.
- a memory interface 10 (of a bridge, for example) may drive lines of a memory bus 11 at time T 0 with signals that indicate a command to activate a page (of the memory bank 12 a ) that contains the memory location. Afterwards, the page is deemed “open.” Next, the memory interface 10 may finish signals (at time T 3 ) that indicate a write command and the column address of the memory location. Subsequently, the memory interface 10 may furnish signals that indicate the data to be written to the memory location.
- the memory interface 10 furnishes signals that indicate another write command, the address and the data, as described below. However, for purposes of writing data into another page of the bank 12 a, the memory interface 10 must first close the bank 12 a via a precharge operation and then activate the bank 12 a (via an activate command) to open the other page before proceeding as described above.
- the memory interface 10 typically determines whether the next command to be issued to a particular memory bank conflicts with a current state of the bank. For example, the memory interface 10 may receive a memory write request. However, before the memory interface 10 communicates a write command to the memory store data in the targeted bank, the memory interface 10 determines if a bank conflict exists so that the memory interface 10 may take the appropriate action before performing the request. As an example, the targeted memory bank may be precharging and thus, cannot perform the write request. Unfortunately, the bank conflict checks may consume a significant amount of time and generally limit the speed in which a sequence of memory access operations may be performed.
- a method for use with a computer system includes determining whether a memory bank is idle and receiving a request to perform a pending operation with the memory bank. If the memory bank is idle, the pending operation is performed with the memory bank without determining whether the pending operation conflicts with a state of the bank.
- a memory interface for use with at least one memory device that includes a bank includes a first circuit, a second circuit and a third circuit.
- the first circuit is adapted to indicate whether the bank is idle
- the second circuit is adapted to determine whether a pending operation with the bank is in conflict with a state of the bank.
- the third circuit is adapted to perform the pending operation with the bank without using the second circuit if the first circuit indicates the bank is idle.
- FIG. 1 is a schematic diagram of a memory subsystem of the prior art.
- FIGS. 2, 3 and 4 are waveforms of memory bus signals of the prior art.
- FIG. 5 is a schematic diagram of a computer system according to an embodiment of the invention.
- FIG. 6 is a schematic diagram of a bridge circuit of the computer system of FIG. 5 according to an embodiment of the invention.
- FIG. 7 is a schematic diagram of a memory interface of the bridge of FIG. 6 according to an embodiment of the invention.
- FIG. 8 is a flow diagram illustrating operation of the memory interface.
- an embodiment 30 of a computer system in accordance with the invention includes a north bridge 34 that serves as an interface to communicate data between buses of the computer system 30 .
- the north bridge 34 may receive pending requests (read and write requests, for example) for operations to be performed with a system memory 44 .
- the pending requests may target memory banks 39 of the system memory 44 that are active and memory banks 39 that are idle.
- the north bridge 34 determines if the pending operation conflicts with a current state of the bank 39 .
- the pending request may be a write request to write data to a particular page of a targeted bank 39 .
- another page of the targeted bank 39 may be open, a condition that requires the north bridge 34 to take the appropriate action before filling this request.
- the north bridge 34 determines that a bank conflict exists and remedies the problem by first precharging the targeted bank 39 (to close the open page). Subsequently, the north bridge 34 activates the targeted bank 39 to open the targeted page, and then the north bridge 34 performs a write operation to the targeted bank 39 satisfy the write request.
- the north bridge 34 may receive a write request that targets a particular bank 39 that is currently precharging. For this scenario, the north bridge 34 determines that a bank conflict exists and remedies the problem by waiting until the precharging is complete. Subsequently, the north bridge 34 activates the targeted bank 39 to open the targeted page and performs a write operation to satisfy the write request. Many other scenarios that cause bank conflicts are possible.
- the bank conflict checks that are performed by the north bridge 34 may consume clock cycles and thus, may increase the latency between successive memory operations.
- the north bridge 34 reduces the number of bank conflict checks by tracking which banks 39 of the system memory 44 are idle. More particularly, in some embodiments, the north bridge 34 includes register bits 106 that indicate which banks 39 are idle and thus, also indicate which banks are active. Because a bank conflict does not occur if the targeted bank 39 is idle, the north bridge 34 does not perform a bank conflict check if the appropriate bit 106 indicates that a particular targeted bank 39 is idle. As a result, the north bridge 34 eliminates some of the bank conflict checks, thereby reducing latency otherwise incurred between successive memory operations due to these checks.
- the number of bits 106 equals the number of banks, and each different bit 106 indicates whether a different associated bank is idle. In other embodiments, the number of bits 106 is less than the number of banks, and each different bit 106 indicates whether a different group of the banks is idle.
- the grouping of the banks depends on the timing of the system 30 .
- the banks may be grouped in fewer groups, as compared to lower frequency memory buses.
- the timing of the memory bus 41 may be programmed via configurations registers (not shown) of the north bridge 34 and may be used to determine the particular grouping that is used.
- the bits 106 are part of a memory interface 92 of the north bridge 34 .
- the memory interface 92 communicates via a memory bus 41 with the system memory 44 to perform typical memory operations, such as read, write and refresh operations, for example.
- the memory interface 92 may also perform bank conflict checks and skip conflict checks for banks that are idle.
- the memory interface 92 may be coupled to other buses of the computer system 30 via multiplexing circuitry 96 .
- a local bus interface 90 (coupled to a local bus 33 ), an Accelerated Graphics Port (AGP) bus interface 98 (coupled to an AGP bus 43 ) and a Peripheral Component Interconnect (PCI) bus interface 94 (coupled to a PCI bus 38 ) may all be coupled together via the multiplexing circuitry 96 .
- AGP Accelerated Graphics Port Interface Specification
- Revision 1.0 published on Jul. 31, 1996, by Intel Corporation of Santa Clara, Calif.
- the PCI Specification is available from the PCI Special Interest Group, Portland, Ore. 97214.
- the memory interface 92 may include a control unit 120 that controls a memory bus interface 112 that communicates with the memory bus 41 , as described below.
- the memory bus interface 112 includes command buffers 117 , data buffers 102 and address buffers 104 to collectively store pending requests that are communicated to the memory interface 92 via the multiplexing circuitry 96 .
- the control unit 120 may also be coupled to the register bits 106 .
- the control unit 120 first determines which bank 39 is to be accessed. Next, the control unit 120 follows a procedure 200 that is depicted in FIG. 8. First, the control unit 120 determines (diamond 202 ) whether the targeted bank 39 is idle. If so, the control unit 120 instructs the bus interface 112 to activate (block 203 ) the targeted bank 39 and subsequently perform the requested operation on the memory bus 41 . However, if the bank 39 is not idle, the control unit 120 performs (block 204 ) a conflict check to determine if the pending request conflicts with a current state of the targeted bank 39 .
- the control unit 120 may determine the state of the bank by examining the contents of a timing chain memory 123 , a memory that stores indications of the most recent operations that have been performed with the bank 39 .
- a timing chain memory 123 indicates, for example, that the targeted bank 39 is precharging, then a bank conflict exists.
- the control unit 120 may also determine if a bank conflict exists by examining the contents of a page status memory 122 . For example, if the page that is targeted by the request is closed then the open page of the bank 39 must be closed (i.e., the bank must be precharged) and the closed page must be activated before the requested operation is performed.
- control unit 120 determines (diamond 206 ) that a bank conflict exists, the controller takes (block 208 ) the appropriate action. Afterwards, the control unit 210 interacts with the bus interface 112 to perform (block 210 ) the pending request. The control unit 120 updates the timing chain memory 123 , the page status memory 122 and the bit registers 106 after each operation.
- the control unit 120 waits for a predetermined amount of time for the precharge to occur and then sets the appropriate bit to indicate that the bank is idle. Conversely, when the control unit 120 activates a bank 39 , the control unit 120 clears the appropriate bit to indicate that the bank 39 is active. Other arrangements are possible.
- the bus interface 112 may also include an address encoder 110 to generate for example, row, column and bank select signals; and strobe generation logic 114 to generate, for example, clock, CAS, RAS and data strobe signals.
- the computer system 30 may include a display controller 45 that is coupled to the AGP bus 43 and generates signals for a display 47 .
- the PCI bus 38 may be coupled to a modem 46 and a south bridge 36 that provides an interface to an input/output (I/O) expansion bus 40 , a CD-ROM drive 50 and the hard disk drive 48 .
- An I/O controller 54 may be coupled to the I/O bus 40 and receive input data from a mouse 56 and a keyboard 58 .
- the I/O controller 54 may also control operations of a floppy disk drive 52 .
- processor may generally refer to at least one central processing unit (CPU, microcontroller or microprocessor, as just a few examples.
- computer system may refer to any type of processor-based system, such as a desktop computer or a laptop computer, as just a few examples.
- the invention is not intended to be limited to the illustrated computer system 30 , but rather, the computer system is an example of one of many possible embodiments.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Memory System (AREA)
Abstract
Description
- The invention relates to processing memory requests that target memory banks.
- Many current computer system memory architectures use synchronous random access memories (synchronous RAMs) such as synchronous dynamic random access memories (SDRAMs), SyncLink dynamic random access memories (SLDRAMs), Rambus dynamic random access memories (RDRAMs) and double data rate (DDR) SDRAM memories. The SyncLink standard has been assigned the tentative designation of IEEE-1596.7 by the Microprocessor & Microcomputer Standards Committee (MMSC) of the Institute of Electrical and Electronics Engineers (IEEE). The Rambus® standard is published by Rambus, Incorporated of Mountain View, Calif.
- In addition to providing inherently faster operation than previous types of memories, synchronous RAM may generally be organized into
memory banks 12, as depicted in FIG. 1. Banks represent a physical compartmentalization of memory space, where each bank may correspond to a unit or array of physical memory. A bank may be further divided into pages, where a page is typically defined in terms of a row address. All those memory locations in a bank having a common row address are said to be on the same page of memory. - One feature of banked memory systems is that consecutive memory access operations to a common page may be performed faster than consecutive memory access operations directed to different pages within the same bank. For example, referring to FIGS. 1, 2,3 and 4, to write data to a memory location of an
idle bank 12 a, a memory interface 10 (of a bridge, for example) may drive lines of amemory bus 11 at time T0 with signals that indicate a command to activate a page (of thememory bank 12 a) that contains the memory location. Afterwards, the page is deemed “open.” Next, thememory interface 10 may finish signals (at time T3) that indicate a write command and the column address of the memory location. Subsequently, thememory interface 10 may furnish signals that indicate the data to be written to the memory location. - If additional data is to be written to another memory location in the open page, then the
memory interface 10 furnishes signals that indicate another write command, the address and the data, as described below. However, for purposes of writing data into another page of thebank 12 a, thememory interface 10 must first close thebank 12 a via a precharge operation and then activate thebank 12 a (via an activate command) to open the other page before proceeding as described above. - The
memory interface 10 typically determines whether the next command to be issued to a particular memory bank conflicts with a current state of the bank. For example, thememory interface 10 may receive a memory write request. However, before thememory interface 10 communicates a write command to the memory store data in the targeted bank, thememory interface 10 determines if a bank conflict exists so that thememory interface 10 may take the appropriate action before performing the request. As an example, the targeted memory bank may be precharging and thus, cannot perform the write request. Unfortunately, the bank conflict checks may consume a significant amount of time and generally limit the speed in which a sequence of memory access operations may be performed. - In one embodiment, a method for use with a computer system includes determining whether a memory bank is idle and receiving a request to perform a pending operation with the memory bank. If the memory bank is idle, the pending operation is performed with the memory bank without determining whether the pending operation conflicts with a state of the bank.
- In another embodiment, a memory interface for use with at least one memory device that includes a bank includes a first circuit, a second circuit and a third circuit. The first circuit is adapted to indicate whether the bank is idle, and the second circuit is adapted to determine whether a pending operation with the bank is in conflict with a state of the bank. The third circuit is adapted to perform the pending operation with the bank without using the second circuit if the first circuit indicates the bank is idle.
- Advantages and other features of the invention will become apparent from the following description, from the drawing and from the claims.
- FIG. 1 is a schematic diagram of a memory subsystem of the prior art.
- FIGS. 2, 3 and4 are waveforms of memory bus signals of the prior art.
- FIG. 5 is a schematic diagram of a computer system according to an embodiment of the invention.
- FIG. 6 is a schematic diagram of a bridge circuit of the computer system of FIG. 5 according to an embodiment of the invention.
- FIG. 7 is a schematic diagram of a memory interface of the bridge of FIG. 6 according to an embodiment of the invention.
- FIG. 8 is a flow diagram illustrating operation of the memory interface.
- Referring to FIG. 5, an
embodiment 30 of a computer system in accordance with the invention includes anorth bridge 34 that serves as an interface to communicate data between buses of thecomputer system 30. For example, thenorth bridge 34 may receive pending requests (read and write requests, for example) for operations to be performed with asystem memory 44. The pending requests may targetmemory banks 39 of thesystem memory 44 that are active andmemory banks 39 that are idle. For anactive bank 39, before performing an operation to fulfill a particular request, thenorth bridge 34 determines if the pending operation conflicts with a current state of thebank 39. - For example, the pending request may be a write request to write data to a particular page of a targeted
bank 39. However, another page of the targetedbank 39 may be open, a condition that requires thenorth bridge 34 to take the appropriate action before filling this request. Thus, for this scenario, thenorth bridge 34 determines that a bank conflict exists and remedies the problem by first precharging the targeted bank 39 (to close the open page). Subsequently, thenorth bridge 34 activates the targetedbank 39 to open the targeted page, and then thenorth bridge 34 performs a write operation to the targetedbank 39 satisfy the write request. - Another example of a bank conflict may be the following. The
north bridge 34 may receive a write request that targets aparticular bank 39 that is currently precharging. For this scenario, thenorth bridge 34 determines that a bank conflict exists and remedies the problem by waiting until the precharging is complete. Subsequently, thenorth bridge 34 activates the targetedbank 39 to open the targeted page and performs a write operation to satisfy the write request. Many other scenarios that cause bank conflicts are possible. - Unfortunately, the bank conflict checks that are performed by the
north bridge 34 may consume clock cycles and thus, may increase the latency between successive memory operations. However, thenorth bridge 34 reduces the number of bank conflict checks by tracking whichbanks 39 of thesystem memory 44 are idle. More particularly, in some embodiments, thenorth bridge 34 includesregister bits 106 that indicate whichbanks 39 are idle and thus, also indicate which banks are active. Because a bank conflict does not occur if the targetedbank 39 is idle, thenorth bridge 34 does not perform a bank conflict check if theappropriate bit 106 indicates that a particular targetedbank 39 is idle. As a result, thenorth bridge 34 eliminates some of the bank conflict checks, thereby reducing latency otherwise incurred between successive memory operations due to these checks. In some embodiments, the number ofbits 106 equals the number of banks, and eachdifferent bit 106 indicates whether a different associated bank is idle. In other embodiments, the number ofbits 106 is less than the number of banks, and eachdifferent bit 106 indicates whether a different group of the banks is idle. - Other arrangements are possible, and the grouping of the banks depends on the timing of the
system 30. For example, for higher frequency memory buses, the banks may be grouped in fewer groups, as compared to lower frequency memory buses. The timing of thememory bus 41 may be programmed via configurations registers (not shown) of thenorth bridge 34 and may be used to determine the particular grouping that is used. - Referring to FIG. 6, in some embodiments, the
bits 106 are part of amemory interface 92 of thenorth bridge 34. Thememory interface 92 communicates via amemory bus 41 with thesystem memory 44 to perform typical memory operations, such as read, write and refresh operations, for example. Thememory interface 92 may also perform bank conflict checks and skip conflict checks for banks that are idle. Thememory interface 92 may be coupled to other buses of thecomputer system 30 viamultiplexing circuitry 96. In this manner, a local bus interface 90 (coupled to a local bus 33), an Accelerated Graphics Port (AGP) bus interface 98 (coupled to an AGP bus 43) and a Peripheral Component Interconnect (PCI) bus interface 94 (coupled to a PCI bus 38) may all be coupled together via themultiplexing circuitry 96. The AGP is described in detail in the Accelerated Graphics Port Interface Specification, Revision 1.0, published on Jul. 31, 1996, by Intel Corporation of Santa Clara, Calif. The PCI Specification is available from the PCI Special Interest Group, Portland, Ore. 97214. - Referring to FIG. 7, in some embodiments, the
memory interface 92 may include acontrol unit 120 that controls amemory bus interface 112 that communicates with thememory bus 41, as described below. Thememory bus interface 112 includes command buffers 117, data buffers 102 and addressbuffers 104 to collectively store pending requests that are communicated to thememory interface 92 via the multiplexingcircuitry 96. Thecontrol unit 120 may also be coupled to theregister bits 106. - For a particular request, the
control unit 120 first determines whichbank 39 is to be accessed. Next, thecontrol unit 120 follows aprocedure 200 that is depicted in FIG. 8. First, thecontrol unit 120 determines (diamond 202) whether the targetedbank 39 is idle. If so, thecontrol unit 120 instructs thebus interface 112 to activate (block 203) the targetedbank 39 and subsequently perform the requested operation on thememory bus 41. However, if thebank 39 is not idle, thecontrol unit 120 performs (block 204) a conflict check to determine if the pending request conflicts with a current state of the targetedbank 39. - In this manner, in some embodiments, the
control unit 120 may determine the state of the bank by examining the contents of atiming chain memory 123, a memory that stores indications of the most recent operations that have been performed with thebank 39. Thus, if thetiming chain memory 123 indicates, for example, that the targetedbank 39 is precharging, then a bank conflict exists. Thecontrol unit 120 may also determine if a bank conflict exists by examining the contents of apage status memory 122. For example, if the page that is targeted by the request is closed then the open page of thebank 39 must be closed (i.e., the bank must be precharged) and the closed page must be activated before the requested operation is performed. - Thus, if the
control unit 120 determines (diamond 206) that a bank conflict exists, the controller takes (block 208) the appropriate action. Afterwards, thecontrol unit 210 interacts with thebus interface 112 to perform (block 210) the pending request. Thecontrol unit 120 updates thetiming chain memory 123, thepage status memory 122 and the bit registers 106 after each operation. - After the
bus interface 112 transmits a command to abank 39 to precharge (and thus, deactivate) thebank 39, thecontrol unit 120 waits for a predetermined amount of time for the precharge to occur and then sets the appropriate bit to indicate that the bank is idle. Conversely, when thecontrol unit 120 activates abank 39, thecontrol unit 120 clears the appropriate bit to indicate that thebank 39 is active. Other arrangements are possible. - Referring back to FIG. 7, besides the components mentioned above, the
bus interface 112 may also include anaddress encoder 110 to generate for example, row, column and bank select signals; andstrobe generation logic 114 to generate, for example, clock, CAS, RAS and data strobe signals. - Referring back to FIG. 5, besides the
north bridge 34 and thesystem memory 44, thecomputer system 30 may include adisplay controller 45 that is coupled to theAGP bus 43 and generates signals for adisplay 47. ThePCI bus 38 may be coupled to amodem 46 and asouth bridge 36 that provides an interface to an input/output (I/O)expansion bus 40, a CD-ROM drive 50 and thehard disk drive 48. An I/O controller 54 may be coupled to the I/O bus 40 and receive input data from amouse 56 and akeyboard 58. The I/O controller 54 may also control operations of afloppy disk drive 52. - In this context of this application, the term “processor” may generally refer to at least one central processing unit (CPU, microcontroller or microprocessor, as just a few examples. The phrase “computer system” may refer to any type of processor-based system, such as a desktop computer or a laptop computer, as just a few examples. Thus, the invention is not intended to be limited to the illustrated
computer system 30, but rather, the computer system is an example of one of many possible embodiments. - While the invention has been disclosed with respect to a limited number of embodiments, those skilled in the art, having the benefit of this disclosure, will appreciate numerous modifications and variations therefrom. It is intended that the appended claims cover all such modifications and variations as fall within the true spirit and scope of the invention.
Claims (15)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/898,277 US6425045B2 (en) | 1999-07-29 | 2001-07-03 | Reducing memory latency by not performing bank conflict checks on idle banks |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/363,604 US6266734B1 (en) | 1999-07-29 | 1999-07-29 | Reducing memory latency by not performing bank conflict checks on idle banks |
US09/898,277 US6425045B2 (en) | 1999-07-29 | 2001-07-03 | Reducing memory latency by not performing bank conflict checks on idle banks |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/363,604 Continuation US6266734B1 (en) | 1999-07-29 | 1999-07-29 | Reducing memory latency by not performing bank conflict checks on idle banks |
Publications (2)
Publication Number | Publication Date |
---|---|
US20010044885A1 true US20010044885A1 (en) | 2001-11-22 |
US6425045B2 US6425045B2 (en) | 2002-07-23 |
Family
ID=23430893
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/363,604 Expired - Lifetime US6266734B1 (en) | 1999-07-29 | 1999-07-29 | Reducing memory latency by not performing bank conflict checks on idle banks |
US09/898,277 Expired - Lifetime US6425045B2 (en) | 1999-07-29 | 2001-07-03 | Reducing memory latency by not performing bank conflict checks on idle banks |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/363,604 Expired - Lifetime US6266734B1 (en) | 1999-07-29 | 1999-07-29 | Reducing memory latency by not performing bank conflict checks on idle banks |
Country Status (1)
Country | Link |
---|---|
US (2) | US6266734B1 (en) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070091696A1 (en) * | 2003-12-09 | 2007-04-26 | Tim Niggemeier | Memory controller |
US20090157993A1 (en) * | 2001-04-17 | 2009-06-18 | Garrett Jr Billy | Mechanism for enabling full data bus utilization without increasing data granularity |
US20090248972A1 (en) * | 2002-06-20 | 2009-10-01 | Ware Frederick A | Dynamic Memory Supporting Simultaneous Refresh and Data-Access Transactions |
US7738496B1 (en) | 2002-12-31 | 2010-06-15 | Cypress Semiconductor Corporation | Device that provides the functionality of dual-ported memory using single-ported memory for multiple clock domains |
US8145809B1 (en) | 2007-03-09 | 2012-03-27 | Cypress Semiconductor Corporation | Busy detection logic for asynchronous communication port |
US8589632B1 (en) * | 2007-03-09 | 2013-11-19 | Cypress Semiconductor Corporation | Arbitration method for programmable multiple clock domain bi-directional interface |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6266734B1 (en) * | 1999-07-29 | 2001-07-24 | Micron Technology, Inc. | Reducing memory latency by not performing bank conflict checks on idle banks |
US6973513B1 (en) * | 2001-04-09 | 2005-12-06 | 3Com Corporation | Method for efficient use of a transmit engine |
US7007133B2 (en) * | 2002-05-29 | 2006-02-28 | Micron Technology, Inc. | Synchronous memory open page register |
US6851032B2 (en) * | 2002-08-16 | 2005-02-01 | Micron Technology, Inc. | Latency reduction using negative clock edge and read flags |
US7934057B1 (en) | 2003-12-24 | 2011-04-26 | Cypress Semiconductor Corporation | Logic for implementing a dual clock domain read access with predictable timing for bi-directional inputs/outputs |
US7299329B2 (en) * | 2004-01-29 | 2007-11-20 | Micron Technology, Inc. | Dual edge command in DRAM |
US20070189084A1 (en) * | 2006-02-15 | 2007-08-16 | Broadcom Corporation | Reduced pin count synchronous dynamic random access memory interface |
US8045416B2 (en) | 2008-03-05 | 2011-10-25 | Micron Technology, Inc. | Method and memory device providing reduced quantity of interconnections |
WO2010101754A2 (en) * | 2009-03-06 | 2010-09-10 | Rambus Inc. | Memory interface with interleaved control information |
TWI541647B (en) * | 2015-02-06 | 2016-07-11 | 瑞昱半導體股份有限公司 | Memory controller and associated control method |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4745545A (en) * | 1985-06-28 | 1988-05-17 | Cray Research, Inc. | Memory reference control in a multiprocessor |
US5412788A (en) * | 1992-04-16 | 1995-05-02 | Digital Equipment Corporation | Memory bank management and arbitration in multiprocessor computer system |
US6026464A (en) * | 1997-06-24 | 2000-02-15 | Cisco Technology, Inc. | Memory control system and method utilizing distributed memory controllers for multibank memory |
JPH1166843A (en) * | 1997-08-08 | 1999-03-09 | Mitsubishi Electric Corp | Semiconductor storage device |
US6266734B1 (en) * | 1999-07-29 | 2001-07-24 | Micron Technology, Inc. | Reducing memory latency by not performing bank conflict checks on idle banks |
-
1999
- 1999-07-29 US US09/363,604 patent/US6266734B1/en not_active Expired - Lifetime
-
2001
- 2001-07-03 US US09/898,277 patent/US6425045B2/en not_active Expired - Lifetime
Cited By (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9257161B2 (en) | 2001-04-17 | 2016-02-09 | Rambus Inc. | Mechanism for enabling full data bus utilization without increasing data granularity |
US9417800B2 (en) | 2001-04-17 | 2016-08-16 | Rambus Inc. | Mechanism for enabling full data bus utilization without increasing data granularity |
US10860216B2 (en) | 2001-04-17 | 2020-12-08 | Rambus Inc. | Mechanism for enabling full data bus utilization without increasing data granularity |
US10146445B2 (en) | 2001-04-17 | 2018-12-04 | Rambus Inc. | Mechanism for enabling full data bus utilization without increasing data granularity |
US8370596B2 (en) * | 2001-04-17 | 2013-02-05 | Rambus Inc. | Mechanism for enabling full data bus utilization without increasing data granularity |
US8856480B2 (en) | 2001-04-17 | 2014-10-07 | Rambus Inc. | Mechanism for enabling full data bus utilization without increasing data granularity |
US20090157993A1 (en) * | 2001-04-17 | 2009-06-18 | Garrett Jr Billy | Mechanism for enabling full data bus utilization without increasing data granularity |
US9824740B2 (en) * | 2002-06-20 | 2017-11-21 | Rambus Inc. | Dynamic memory supporting simultaneous refresh and data-access transactions |
US10593390B2 (en) | 2002-06-20 | 2020-03-17 | Rambus Inc. | Dynamic memory supporting simultaneous refresh and data-access transactions |
US20090248972A1 (en) * | 2002-06-20 | 2009-10-01 | Ware Frederick A | Dynamic Memory Supporting Simultaneous Refresh and Data-Access Transactions |
US7738496B1 (en) | 2002-12-31 | 2010-06-15 | Cypress Semiconductor Corporation | Device that provides the functionality of dual-ported memory using single-ported memory for multiple clock domains |
US7873797B2 (en) * | 2003-12-09 | 2011-01-18 | Thomson Licensing | Memory controller |
US20070091696A1 (en) * | 2003-12-09 | 2007-04-26 | Tim Niggemeier | Memory controller |
US8145809B1 (en) | 2007-03-09 | 2012-03-27 | Cypress Semiconductor Corporation | Busy detection logic for asynchronous communication port |
US8589632B1 (en) * | 2007-03-09 | 2013-11-19 | Cypress Semiconductor Corporation | Arbitration method for programmable multiple clock domain bi-directional interface |
Also Published As
Publication number | Publication date |
---|---|
US6425045B2 (en) | 2002-07-23 |
US6266734B1 (en) | 2001-07-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6272609B1 (en) | Pipelined memory controller | |
US6295592B1 (en) | Method of processing memory requests in a pipelined memory controller | |
US6266734B1 (en) | Reducing memory latency by not performing bank conflict checks on idle banks | |
US6026464A (en) | Memory control system and method utilizing distributed memory controllers for multibank memory | |
US6681302B2 (en) | Page open hint in transactions | |
US6640292B1 (en) | System and method for controlling retire buffer operation in a memory system | |
US5022004A (en) | Method and apparatus for DRAM memory performance enhancement | |
US6587918B1 (en) | Method for controlling refresh of a multibank memory device | |
US6298413B1 (en) | Apparatus for controlling refresh of a multibank memory device | |
US5822768A (en) | Dual ported memory for a unified memory architecture | |
US6182192B1 (en) | Memory interface device and method for accessing memories | |
JPH09213070A (en) | Hidden ) type pseudcache dram | |
US6564284B2 (en) | Apparatus for controlling a multibank memory device | |
US6389520B2 (en) | Method for controlling out of order accessing to a multibank memory | |
US6535966B1 (en) | System and method for using a page tracking buffer to reduce main memory latency in a computer system | |
US7159066B2 (en) | Precharge suggestion | |
US5893917A (en) | Memory controller and method of closing a page of system memory | |
US6360305B1 (en) | Method and apparatus for optimizing memory performance with opportunistic pre-charging | |
US6948046B2 (en) | Access controller that efficiently accesses synchronous semiconductor memory device | |
KR100297895B1 (en) | Method and apparatus for controlling data transfer between a synchronous dram-type memory and a system bus | |
US6622203B2 (en) | Embedded memory access method and system for application specific integrated circuits | |
US6442645B1 (en) | Pre-decode conditional command generation for reduced SDRAM cycle latency | |
US5274786A (en) | Microprocessor memory bus interface for inhibiting relatching of row address portions upon subsequent accesses including a same row address portion | |
US6385687B2 (en) | Method and apparatus for simultaneously accessing the tag and data arrays of a memory device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: FLEET CAPITAL CANADA CORPORATION, CANADA Free format text: SECURITY INTEREST;ASSIGNORS:NORTEK, INC.;BROAN-NUTONE LLC, LIMITED LIABILITY COMPANY - DELAWARE;NUTONE INC., CORPORATION - DELAWARE;AND OTHERS;REEL/FRAME:013516/0374 Effective date: 20020725 Owner name: FLEET CAPITAL CORPORATION, NEW YORK Free format text: SECURITY INTEREST;ASSIGNORS:NORTEK, INC.;BROAN-NUTONE LLC, LIMITED LIABILITY COMPANY - DELAWARE;NUTONE INC., CORPORATION - DELAWARE;AND OTHERS;REEL/FRAME:013516/0374 Effective date: 20020725 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
AS | Assignment |
Owner name: ROUND ROCK RESEARCH, LLC,NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICRON TECHNOLOGY, INC.;REEL/FRAME:023786/0416 Effective date: 20091223 Owner name: ROUND ROCK RESEARCH, LLC, NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICRON TECHNOLOGY, INC.;REEL/FRAME:023786/0416 Effective date: 20091223 |
|
FPAY | Fee payment |
Year of fee payment: 12 |