Memory Access and Detecting Memory Failures using Dynamically Replicated Memory
AssigneeMicrosoft Technology Licensing, LLC
InventorsEngin Ipek, Douglas Christopher Burger, Thomas Moscibroda, Edmund Bernard Nightingale, Jeremy P. Condit
Life of this patent
Estimating the term…
Abstract
Dynamically replicated memory is usable to allocate new memory space from failed memory pages by pairing compatible failed memory pages to reuse otherwise unusable failed memory pages. Dynamically replicating memory involves detecting and recording memory faults, reclaiming failed memory pages for later use, recovering from detected memory faults, and scheduling access to replicated memory pages.
Claims21
(canceled)
One or more computer-readable storage media storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform acts comprising:
- receiving a memory access request for data from a memory controller, the data being included in a set of faulty memory pages including at least a first memory page and a second memory page, wherein the first memory page includes a failed memory block that is located at a relative position different from a failed memory block of the second memory page;
- and
- sending a first data request for data of the first memory page and a second data request for data of the second memory page.
A system comprising:
- memory and one or more processors;
- a memory controller module stored in the memory and executable by the one or more processors to make memory write requests for data included in a set of faulty memory pages including at least a primary memory page and a duplicate memory page, at least one failed memory block of the primary memory page being located at a relative position different from a failed memory block of the duplicate memory page;
- and
- a transaction queue module to store the memory write requests.
A method comprising:
- receiving an incoming memory access request for data from a memory controller, the data being included in a set of faulty memory pages including at least a first memory page and a second memory page, at least one failed memory block of the first memory page being located at a relative position different from a failed memory block of the second memory page;
- placing a first memory access request for data of the first memory page and a second memory access request for data of the second memory page;
- receiving the data of the first memory page at the memory controller;
- and
- waiting to receive the data of the second memory page in response to determining that the data of the first memory page is faulty.
Dependencies are inferred from the claim text.