SYSTEM AND METHOD FOR RETAINING DRAM DATA WHEN REPROGRAMMING RECONFIGURABLE DEVICES WITH DRAM MEMORY CONTROLLERS INCORPORATING A DATA MAINTENANCE BLOCK COLOCATED WITH A MEMORY MODULE OR SUBSYSTEM

Abstract

A system and method for retaining dynamic random access memory (DRAM) data when reprogramming reconfigurable devices with DRAM memory controllers such as field programmable gate arrays (FPGAs). The DRAM memory controller is utilized in concert with a data maintenance block collocated with the DRAM memory and coupled to an I2C interface of the reconfigurable device, wherein the FPGA drives the majority of the DRAM input/output (I/O) and the data maintenance block drives the self-refresh command inputs. Even though the FPGA reconfigures and the majority of the DRAM inputs are tri-stated, the data maintenance block provides stable input levels on the self-refresh command inputs.

Description

CROSS REFERENCE TO RELATED PATENT APPLICATIONS

The present application is a divisional of, and claims priority to, U.S. patent application Ser. No. 14/834,273, entitled “System and Method for Retaining DRAM Data When Reprogramming Reconfigurable Devices with DRAM Memory Controllers Incorporating a Data Maintenance Block Colocated with a Memory Module or Subsystem” filed Aug. 24, 2015, which is a continuation-in-part of, and claims priority to, U.S. Pat. No. 9,153,311, entitled “System and Method for Retaining DRAM Data When Reprogramming Reconfigurable Devices with DRAM Memory Controllers” which was issued on Oct. 6, 2015, the disclosures of which are both herein incorporated in their entirety by this reference.

BACKGROUND

The present invention relates, in general, to the field of reconfigurable computing systems. More particularly, the present invention relates to a system and method for retaining dynamic random access memory (DRAM) data when reprogramming reconfigurable devices with DRAM memory controllers incorporating a data maintenance block collocated with a memory module or subsystem. In a further alternative embodiment of the present invention, a memory subsystem implemented in persistent memory is provided which utilizes a communication port coupled to a reconfigurable memory controller that advises the controller as to the current state of the memory as required by the controller.

The majority of today's programmable logic designs include a DRAM based memory solution at the heart of their memory subsystem. Today's DRAM devices are significantly faster than previous generation's, albeit at the cost of requiring increasingly complex and resource intensive memory controllers. One example is in double data rate 3 and 4 (DDR3 and DDR4) controllers which require read and write calibration logic. This added logic was not necessary when using previous versions of DRAM (e.g. DDR and DDR2. As a result, companies are forced to absorb substantial design costs and increased project completion times when designing proprietary DRAM controllers utilizing modern DRAM technology.

In order to mitigate design engineering costs and verification time, it is very common for field programmable gate array (FPGA) designers to implement vendor provided memory controller intellectual property (IP) when including DRAM based memory solutions in their designs. See, for example, Allan, Graham; “DDR IP Integration: How to Avoid Landmines in this Quickly Changing Landscape”; Chip Design, June/July 2007; pp 2022 and Wilson, Ron; “DRAM Controllers for System Designers”; Altera Corporation Articles, 2012.

FPGA designers tend to choose device manufacturer IP designs because they are proven, tested and have the incredible benefit of significantly reduced design costs and project completion times. Many times there is the added benefit of exploiting specialized circuitry within the programmable device to increase controller performance, which is not always readily apparent when designing a controller from scratch.

The downside to using factory supplied IP memory controllers is that there is little flexibility when trying to modify operating characteristics. A significant problem arises in reconfigurable computing when the FPGA is reprogrammed during a live application and the memory controller tri-states all inputs and outputs (I/O) between the FPGA device and the DRAM. The result is corrupted data in the memory subsystem. Therefore, dynamically reconfigurable processors are excluded as viable computing options, especially in regard to database applications or context switch processing. The reason for this is that the time it takes to copy the entire contents of DRAM data and preserve it in another part of the system, reconfigure the processor, then finally retrieve the data and restore it in DRAM is just too excessive.

Current state of the art reconfigurable computing systems will generally commence operations from a reset condition after the system is configured and initialize non-persistent (or volatile) memory subsystem. However, much development of enhancing persistent memory subsystems is currently underway. See for example, Lee, B. C. et al.; “Architecting Phase Change Memory as a Scalable DRAM Alternative”; ISCA June 2009. Persistent memories have the benefit of maintaining previously processed data when reconfiguring or hot-swapping memory controllers.

After reconfiguration, it would be beneficial for the processor section of the system to know the current status of the memory subsystem before it begins initializing the memory, especially in a context switch operation where the processor might require using the same data set between reconfigurations.

SUMMARY

Disclosed herein is a system and method for preserving DRAM memory contents when a reconfigurable device, for example an FPGA having a DRAM memory controller, is reconfigured, reprogrammed or otherwise powered down. When an FPGA is reprogrammed, the DRAM inputs are tri-stated including self-refresh command signals. Indeterminate states on the reset or clock enable inputs results in DRAM data corruption.

In accordance with the system and method of the present invention, an FPGA based DRAM controller is utilized in concert with an internally or externally located data maintenance block, including being collocated on an associated memory module. In operation, the FPGA drives the majority of the DRAM input/output (I/O) and the data maintenance block drives the self-refresh command inputs. Even though the FPGA reconfigures and the majority of the DRAM inputs are tri-stated, the data maintenance block provides stable input levels on the self-refresh command inputs.

Functionally, the data maintenance block does not contain the memory controller and therefore has no point of reference for when and how to initiate the self-refresh commands, particularly the DRAM self-refresh mode. As also disclosed herein, a communication port is implemented between the FPGA and the data maintenance block that allows the memory controller in the FPGA to direct the self-refresh commands to the DRAM via the data maintenance block. Specifically, this entails when to put the DRAM into self-refresh mode and preserve the data in memory.

At this point, the DRAM data has been preserved throughout the FPGA reconfiguration via the self-refresh 5 mode initiated by the data maintenance block, but the DRAM controller must now re-establish write/read timing windows and will corrupt specific address contents with guaranteed write and read data required during the calibration/leveling process. Consequently, using the 10 self-refresh capability of DRAM alone is not adequate for maintaining data integrity during reconfiguration. (It should be noted that the memory addresses used during calibration/leveling are known and typically detailed in the controller IP specification).

In order to effectuate this, the system transmits a “reconfiguration request” to the DRAM controller. Once received, glue logic surrounding the FPGA vendor provided memory controller IP issues read requests to the controller specifying address locations used during the calibration/leveling process. As data is retrieved from the DRAM, it is transmitted via the communication port from the FPGA device to a block of storage space residing within the data maintenance block itself or another location in the system.

Once the process is complete, the data maintenance block sends a self-refresh command to the DRAM and transmits an acknowledge signal back to the FPGA. The data maintenance block recognizes this as an FPGA reconfiguration condition versus an FPGA initial power up condition and retains this state for later use.

Once the FPGA has been reprogrammed, the DRAM controller has re-established calibration settings and several specific addresses in the DRAM have been corrupted with guaranteed write/read data patterns. At this point, glue logic surrounding the vendor memory controller IP is advised by the data maintenance block (through the communication port) that it has awakened from either an initial power up condition or a reconfiguration condition. If a reconfiguration condition is detected, and before processing incoming DMA requests, the controller retrieves stored DRAM data from the data maintenance block (again through the communication port) and writes it back to the specific address locations corrupted during the calibration/leveling process. Once complete, the DRAM controller in the FPGA is free to begin servicing system memory requests in the traditional fashion.

Among the benefits provided in conjunction with the system and method of the present invention is that since the data maintenance block functions to hold the DRAM in self-refresh mode, the FPGA is free to be reprogrammed to perform a very application-specific computing job that may not require DRAM. This means all the device resources previously reserved for creating a DRAM controller are now free to be used for different functions.

Further, the overall computer system benefits from the present invention because data previously stored in DRAM has now been preserved and is available for use by the next application that needs it. This leads to the fact that computing solutions requiring a series of specific data manipulation tasks now have the ability to be implemented in a small reconfigurable processor. Each application performs its intended function and data is passed from application to application between reconfiguration periods via the DRAM.

Importantly, it should also be noted that the DRAM data contents are retained even if the reconfigurable device is powered down. This is especially critical, for example, when the system and method of the present invention is implemented in mobile devices.

In a particular embodiment of the present invention disclosed herein, a system and method is provided for use in a reconfigurable computing environment in hardware, without the need for software intervention.

By incorporating a block of logic and/or memory with a communication port dedicated to updating and maintaining the current state of the memory subsystem within the memory subsystem, upon reconfiguration, the processor will be able to query the memory subsystem and receive the information required to determine how to proceed with respect to accessing the memory subsystem. Such information may include the memory subsystem's state of initialization or readiness, base and limit addresses table lookaside buffer (TLB) mapping contents and the like. This information may be sent out the communications port by the memory controller in real-time and stored in the memory subsystem or it might only be used just before the processor is reconfigured.

A fundamental benefit of this system and method is 30 that, in a persistent memory subsystem, the information held can be quickly transferred back to the memory controller after reconfiguration or a hot swap operation. Advances in new memory technologies such as FLASH and phase change memory (PCM) are capable of creating memory subsystems at the multiple terabyte levels making data persistence all the more important due to ever increasing load times at system boot. The incorporation of this type of persistent memory subsystem to a reconfigurable computing system is enabled by the provision of a fast, tightly coupled port to the memory subsystem for retrieving memory subsystem status which, in turn, shortens the overall start up time following reconfiguration.

Particularly disclosed herein is a computer system comprising a DRAM memory, a reconfigurable logic device having a memory controller coupled to selected inputs and outputs of said DRAM memory and a data maintenance block collocated with the DRAM memory and coupled to the reconfigurable logic device and self-refresh command inputs of the DRAM memory. The data maintenance block is operative to provide stable input levels on the self-refresh command inputs while the reconfigurable logic device is reconfigured.

Also particularly disclosed herein is a method for preserving contents of a DRAM memory associated with a reconfigurable device having a memory controller comprising providing a data maintenance block collocated with the DRAM memory, the data maintenance block being coupled to the reconfigurable device; coupling the data maintenance block to self-refresh command inputs of the DRAM memory; storing data received from the reconfigurable device at the data maintenance block; and maintaining stable input levels on the self-refresh command inputs while the reconfigurable logic device is reconfigured.

Still further particularly disclosed herein is a computer system which comprises a reconfigurable processor comprising a number of processing elements, a memory subsystem query controller and a reconfigurable memory controller and a memory subsystem comprising a plurality of memory storage elements and an associated subsystem status information block, the reconfigurable memory controller is coupled to the memory storage elements and the memory subsystem query controller is coupled to the subsystem status information block and the reconfigurable memory controller wherein the subsystem status information block is operative to provide a current state of the memory subsystem to the reconfigurable memory controller.

BRIEF DESCRIPTION OF THE DRAWINGS

The aforementioned and other features and objects of the present invention and the manner of attaining them will become more apparent and the invention itself will be best understood by reference to the following description of a preferred embodiment taken in conjunction with the accompanying drawings, wherein:

FIG. 1 is a functional block diagram of a computer subsystem comprising a reconfigurable logic device having a reconfigurable DRAM controller with associated DRAM memory and illustrating the data maintenance block of the present invention for retaining DRAM data when the logic device is reconfigured;

FIG. 2 is a block diagram of a reconfigurable computer system, incorporating a pair of data maintenance blocks and DRAM memory in accordance with the system and method of the present invention in association with reconfigurable application logic;

FIG. 3 is a functional block diagram of an alternative embodiment of a computer subsystem comprising a reconfigurable logic device having a reconfigurable DRAM controller with associated DRAM memory and illustrating the data maintenance block of the present invention being located on the SDRAM memory subassembly; and,

FIG. 4 is a functional block diagram of another possible embodiment of a computer subsystem in accordance with the principles of the present invention wherein a reconfigurable processor comprises a memory subsystem query controller for interfacing with a subsystem status information block associated with the memory subsystem.

DESCRIPTION OF A REPRESENTATIVE EMBODIMENT

With reference now to FIG. 1, a functional block diagram of a computer subsystem 100 comprising a DRAM memory 102 and reconfigurable logic device 104 is shown. In a representative embodiment of the present invention, the reconfigurable logic device 104 may comprise a field programmable gate array (FPGA). However, it should be noted that the reconfigurable logic device 104 may comprise any and all forms of reconfigurable logic devices including hybrid devices, such as a reconfigurable logic device with partial reconfiguration capabilities or an application specific integrated circuit (ASIC) device with reprogrammable regions contained within the chip.

Also illustrated is a data maintenance block 106 in accordance with the present invention for retaining DRAM memory 102 data when the logic device 104 is reconfigured during operation of the computer subsystem 100. In a representative embodiment of the present invention, the data maintenance block 106 may be conveniently provided as a complex programmable logic device (CPLD) or other separate integrated circuit device or, in alternative embodiments, may be provided as a portion of an FPGA comprising the reconfigurable logic device 104.

As illustrated, the reconfigurable logic device 104 comprises a primary system logic block 108 which issues a reconfigure request command to a reconfigure controller 110 and receives a reconfigure request acknowledgement (Ack) signal in return. The reconfigure controller 110, in turn, issues a command to the command decode block 112 of the data maintenance block 106 and receives an acknowledgement (Ack) signal in return. A block RAM portion 114 of the data maintenance block 106 exchanges data with the reconfigure controller 110.

The reconfigure controller 110 receives an input from a refresh timer 116 which is coupled to receive row address select (RAS#), column address select (CAS#) and write enable (WE#) signals from a memory controller and physical interface block 118. The memory controller and physical interface block 118 also provides the RAS#, CAS# and WE# signals to the DRAM memory 102 as well as clock (CK, CK#), chip select (CS#), address (A), bank address (BA), data mask (DM) and on-die termination (ODT) input signals. Bidirectional data (DQ) input/output (I/O) and differential data strobe signals (DQS/DQS#) are exchanged between the DRAM memory 102 and the memory controller and physical interface block 118 as shown. The data maintenance block 106 is coupled to the DRAM memory 102 to supply reset (RESET#) and clock enable (CKE#) signals thereto.

The memory controller and physical interface block 118 responds to a request from the controller interface 120 to provide data read from the DRAM memory 102 (Rd Data) and to receive data to be written to the DRAM memory 102 (Wr Data) as shown. A source logic block 122 is coupled to the controller interface 120 as well as the reconfigure controller 110 as also illustrated. The source logic block 122 receives a data request from the primary system logic block 108 and supplies data read from the DRAM memory 102 while receiving data to be written thereto.

As indicated by the operation at numeral 1, a reconfiguration request is received at the reconfigure controller 110 from the primary system logic block 108 of the reconfigurable logic device 104. The reconfigure controller 110 initiates direct memory access (DMA) read requests to memory addresses used in a calibration/leveling sequence after the reconfigurable logic device 104 is reconfigured. Returned data is stored in a small section of block RAM (not shown) in the reconfigure controller 110.

As indicated by the operation at numeral 2, the reconfigure Controller 110 stores its block RAM contents in another small section of block RAM 114 located in the data maintenance block 106. When complete, the data maintenance block 106 asserts an acknowledge signal from its command decode block 112. At the operation indicated by numeral 3, the reconfigure controller 110 detects a refresh command from the refresh timer 116, waits a refresh cycle time (tRFc) and instructs the data maintenance block 106 to de-assert CKE to the DRAM memory 102.

The reconfigure controller 110 asserts the Reconfigure Request Ack signal at the operation indicated by numeral 4 and the reconfigurable logic device 104 is reconfigured. As indicated by the operation at numeral 5, the reconfigure controller 110 recognizes a post-reconfigure condition (Ack=High), holds the memory controller and physical interface 118 in reset and instructs the data maintenance block 106 to assert CKE to the DRAM memory 102. The memory controller and physical interface 118 is then released from reset and initializes the DRAM memory 102.

At the operation indicated by numeral 6, the reconfigure controller 110 retrieves the data maintenance block 106 block RAM 114 contents and stores it in a small section of block RAM (not shown) in the reconfigure controller 110. The reconfigure controller 110 detects that the memory controller and physical interface 118 and DRAM memory 102 initialization is complete at the operation indicated by numeral 7 and initiates DMA write requests to restore the memory contents corrupted during the calibration/leveling sequence with the data values read prior to reconfiguration. At the operation indicated by numeral 8, the memory controller and physical interface 118 glue logic (comprising reconfigure controller 110, refresh timer 116, controller interface 120 and source logic block 122) resumes DMA activity with the primary system logic 108 in a conventional fashion.

It should be noted certain of the aforementioned operational steps may, in fact, operate substantially concurrently. Further, while functionally accurate, some of the operational steps enumerated have been listed out of order to provide logical continuity to the overall operation and to facilitate comprehensibility of the process. In a particular implementation of the system and method of the present invention, one or more of the operational steps disclosed may be conveniently reordered to increase overall hardware efficiency. Moreover, steps which can serve to facilitate relatively seamless integration in an active application can be provided in addition to those described as may be desired.

With reference additionally now to FIG. 2, a block diagram of a reconfigurable computer system 200 is illustrated incorporating a pair of data maintenance blocks 106 and DRAM memory 102 in accordance with the system and method of the present invention in association with reconfigurable application logic 202. In this representative embodiment of a reconfigurable computer system 200, the DRAM memory 102 is illustrated in the form of 32 GB error correction code (ECC) synchronous dynamic random access memory (SDRAM).

The reconfigurable application logic 202 is coupled to the data maintenance blocks 106 and DRAM memory 102 as depicted and described previously with respect to the preceding figure and is also illustrated as being coupled to a number of 8 GB ECC static random access memory (SRAM) memory modules 204. The reconfigurable application logic 202 is also coupled to a SNAP™ and network processors block 206 having a number of serial gigabit media independent interface (SGMII) links as shown. It should be noted that the DRAM memory 102 controller in the reconfigurable application block 202 may be omitted upon subsequent reconfigurations as the DRAM memory 102 data contents will be maintained in the data maintenance blocks 106.

The SNAP and network processors block 206 shares equal read/write access to a 1 GB peer SDRAM system memory 208 along with a microprocessor subsystem 210. The microprocessor subsystem 210, as illustrated, also comprises an SGMII link as well as a pair of serial advanced technology attachment (SATA) interfaces.

With reference additionally now to FIG. 3, a functional block diagram of an alternative embodiment of a computer subsystem 300 is shown comprising a reconfigurable logic device 104 having a reconfigurable DRAM controller with associated DRAM memory 102 and illustrating the data maintenance block 106 of the present invention being co-located on the SDRAM memory subassembly. As Illustrated, the DRAM memory 102 comprises, in pertinent part, a serial presence detect (SPD) EEPROM 203 and a number of volatile memory storage elements 304. The DRAM memory 102 is also illustrated as being coupled to receive address inputs SAO, SA1 and SA2.

In this particular embodiment of the computer subsystem 300, the reconfigure controller 310 is functionally the same as the reconfigure controller 110 described and illustrated with respect to the preceding figures but also comprises an inter-integrated circuit (I2C) interface including serial data lines (SDA) and serial clock lines (SCL) for communications between the reconfigure controller 310 and the data maintenance block 106. With respect to other aspects of the computer subsystem 300 illustrated, like structure to that previously disclosed and described with respect to the preceding figures is like numbered and the foregoing description thereof shall suffice here for.

As indicated by the operation at numeral 1, a reconfiguration request is received and the reconfigure controller 310 initiates DMA read requests to memory addresses used in the calibration/leveling sequence after the reconfigurable logic device 104 is reconfigured. As further indicated by the operation at numeral 2, returned data is sent to the DRAM memory 102 DIMM module via the I2C bus and stored in the data maintenance block 106 or unused portions of the SPD EEPROM 302. With respect to the operations depicted by numerals 3 through 8, these operations are essentially as previously described in conjunction with the embodiment of the computer subsystem 100 of FIG. 1.

Once more, it should be noted that certain of the aforementioned operational steps may, in fact, operate substantially concurrently. Further, while functionally accurate, some of the operational steps enumerated have been listed out of order to provide logical continuity to the overall operation and to facilitate comprehensibility of the process. In a particular implementation of the system and method of the present invention, one or more of the operational steps disclosed may be conveniently re-ordered to increase overall hardware efficiency. Moreover, steps which can serve to facilitate relatively seamless integration in an active application can be provided in addition to those described as may be desired.

In this alternative embodiment of the present invention, the reconfigurable logic device 104 may, as with the embodiment of FIG. 1, comprise an FPGA. However, it should be noted that the reconfigurable logic device 104 may again comprise any and all forms of reconfigurable logic devices including hybrid devices, such as a reconfigurable logic device with partial reconfiguration capabilities or an ASIC device with reprogrammable regions contained within the chip.

As before, the data maintenance block 106 in accordance with the present invention functions to retain DRAM memory 102 data when the logic device 104 is reconfigured during operation of the computer subsystem 300. In a representative embodiment of the present invention, the data maintenance block 106 may be conveniently provided as co-located on the DRAM memory 102 (e.g. an SDRAM DIMM module) itself whether as part of the storage silicon itself or as a die stacked in what is an already stacked memory device.

In operation, the memory controller 118 can utilize the I2C bus as a communications port to submit power up/down requests and data to/from the data maintenance block 106. In this manner, the need for a separate set of pins or wires to the data maintenance block is obviated. As a practical matter, FPGA memory controller IP typically does not utilize the SPD information from the DIMM module and the designer must determine ahead of time the memory timings and topology and configure the controller IP to that single specification. In the event the I2C bus is used by the controller, a sniffer circuit in the data maintenance block 106 may be employed to monitor the I2C bus traffic and enable a determination as to when a reconfigure process was forthcoming. In this regard, the data maintenance block 106 might employ a bogus I2C protocol unrecognizable by the EEPROM to prevent possible corruption of its contents.

With the use of the existing I2C serial bus for communications between the memory controller 118 and the DIMM DRAM memory 102, the data maintenance block 106 has the additional task of controlling serial presence detect contents from the SPD EEPROM 302 at memory initialization time. Moreover, by incorporating the data maintenance block 106 in the DRAM memory 102, SDRAM memory persistence may be maintained when “hot-swapping” the reconfigurable logic device 104 containing the reconfigure controller 310 with a different reconfigurable logic device 104 comprising a reconfigure controller 310.

With reference additionally now to FIG. 4, a functional block diagram of another possible embodiment 5 of a computer subsystem 400 in accordance with the principles of the present invention is shown wherein a reconfigurable processor 402 comprises a memory subsystem query controller 408 for interfacing with a subsystem status information block 410 associated with 10 the memory subsystem 404. As illustrated, the reconfigurable processor 402 comprises various processing elements 406 and a reconfigurable memory controller 412 in communication with the memory subsystem query controller 408 and the primary memory 15 storage elements 414 in the memory subsystem 404

The embodiments of the computer subsystems of the preceding FIGS. 1-3 effectively provide persistent, reconfigurable computer system memory utilizing non-persistent DRAM. In distinction, the computer subsystem 400 is configured utilizing inherently persistent memory such as NAND Flash, PCM, FeRAM, 3D Xpoint or the like for the primary memory storage elements 414 while incorporating a piece of logic and RAM in a discrete block located on a memory device, module or subsystem such as the subsystem status information block 410. A communication port couples the subsystem status information block 410 to a memory subsystem query controller 408 in the reconfigurable processor 402.

During runtime, a portion of the reconfigurable memory controller 412 transmits status information to the memory subsystem 404 while the subsystem status information block 410 is responsible for updating and maintaining data received from the controller. After the reconfigurable processor 402 completes a first task, it will be reconfigures and begin the next task. Before it initializes the memory, the controller will query the memory as to the previous status and, as a result, receive information as to when, how, where and the lie to begin the next task. When queried, the memory might provide a response indicating that it is already initialized and ready and indicate to the processor that, prior to its reconfiguration, the task involved a given data set located, for example, at a specified base address. The memory might also indicate the state of the reconfigurable processor 402 TLB mapping and send a copy to the processor so that it can be recreated unless the same as before. At this point, the reconfigurable processor 402 can begin running its user code.

For continuity and clarity of the description herein, the term “FPGA” has been used in conjunction with the representative embodiment of the system and method of the present invention and refers to just one type of reconfigurable logic device. However, it should be noted that the concept disclosed herein is applicable to any and all forms of reconfigurable logic devices including hybrid devices, inclusive of reconfigurable logic devices with partial reconfiguration capabilities or an ASIC device with reprogrammable regions contained within the chip.

Representative embodiments of dynamically reconfigurable computing systems incorporating the DRAM memory 102, reconfigurable logic device 104, associated microprocessors and programming techniques are disclosed in one or more of the following United States Patents and United States Patent Publications, the disclosures of which are herein specifically incorporated by this reference in their entirety: U.S. Pat. No. 6,026,459; U.S. Pat. No. 6,076,152; U.S. Pat. No. 6,247,110; U.S. Pat. No. 6,295,598; U.S. Pat. No. 6,339,819; U.S. Pat. No. 6,356,983; U.S. Pat. No. 6,434,687; U.S. Pat. No. 10 6,594,736; U.S. Pat. No. 6,836,823; U.S. Pat. No. 6,941,539; U.S. Pat. No. 6,961,841; U.S. Pat. No. 6,964,029; U.S. Pat. No. 6,983,456; U.S. Pat. No. 6,996,656; U.S. Pat. No. 7,003,593; U.S. Pat. No. 7,124,211; U.S. Pat. No. 7,134,120; U.S. Pat. No. 15 7,149,867; U.S. Pat. No. 7,155,602; U.S. Pat. No. 7,155,708; U.S. Pat. No. 7,167,976; U.S. Pat. No. 7,197,575; U.S. Pat. No. 7,225,324; U.S. Pat. No. 7,237,091; U.S. Pat. No. 7,299,458; U.S. Pat. No. 7,373,440; U.S. Pat. No. 7,406,573; U.S. Pat. No. 20 7,421,524; U.S. Pat. No. 7,424,552; U.S. Pat. No. 7,565,461; U.S. Pat. No. 7,620,800; U.S. Pat. No. 7,680,968; U.S. Pat. No. 7,703,085; U.S. Pat. No. 7,890,686; U.S. Pat. No. 8,589,666; U.S. Pat. Pub. No. 2012/0117318; U.S. Pat. Pub. No. 2012/0117535; and U.S. 25 Pat. Pub. No. 2013/0157639. While there have been described above the principles of the present invention in conjunction with specific apparatus and methods, it is to be clearly understood that the foregoing description is made only by way of example and not as a limitation to the scope of the invention. Particularly, it is recognized that the teachings of the foregoing disclosure will suggest other modifications to those persons skilled in the relevant art. Such modifications may involve other features which are already known per se and which may be used instead of or in addition to features already described herein. Although claims have been formulated in this application to particular combinations of features, it should be understood that the scope of the disclosure herein also includes any novel feature or any novel combination of features disclosed either explicitly or implicitly or any generalization or modification thereof which would be apparent to persons skilled in the relevant art, whether or not such relates to the same invention as presently claimed in any claim and whether or not it mitigates any or all of the same technical problems as confronted by the present invention. The applicants hereby reserve the right to formulate new claims to such features and/or combinations of such features during the prosecution of the present application or of any further application derived therefrom.

As used herein, the terms “comprises”, “comprising”, or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a recitation of certain elements does not necessarily include only those elements but may include other elements not expressly recited or inherent to such process, method, article or apparatus. None of the description in the present application should be read as implying that any particular element, step, or function is an essential element which must be included in the claim scope and THE SCOPE OF THE PATENTED SUBJECT MATTER IS DEFINED ONLY BY THE CLAIMS AS ALLOWED. Moreover, none of the appended claims are intended to invoke paragraph six of 35 U.S.C. Sect. 112 unless the exact phrase “means for” is employed and is followed by a participle.

Claims

1. A computer system comprising:

a reconfigurable processor comprising a number of processing elements, a memory subsystem query controller and a reconfigurable memory controller; and

a memory subsystem comprising a plurality of memory storage elements and an associated subsystem status information block, said reconfigurable memory controller being coupled to said memory storage elements and said memory subsystem query controller being coupled to said subsystem status information block and said reconfigurable memory controller wherein said subsystem status information block is operative to provide a current state of said memory subsystem to said reconfigurable memory controller.

2. The computer system of claim 1 wherein said reconfigurable processor comprises an FPGA.

3. The computer system of claim 1 wherein said memory storage elements comprise persistent memory.

4. The computer system of claim 3 wherein said persistent memory comprises at least one of NAND Flash, PCM, FeRAM or 3D Xpoint memory.

5. The computer system of claim 1 wherein said current state of said memory subsystem comprises at least one of a state of initialization or readiness, base and limit addresses or table lookaside buffer mapping contents of said memory subsystem.

6. The computer system of claim 1 wherein the memory subsystem query controller is collocated within the reconfigurable processor.

7. The computer system of claim 1 wherein the memory subsystem query controller is collocated within the reconfigurable memory controller.

8. The computer system of claim 1 wherein memory subsystem queries are performed by the reconfigurable processor.

9. The computer system of claim 1 wherein memory subsystem queries are performed by the reconfigurable memory controller.

10. The computer system of claim 1 wherein said current state of said memory subsystem comprises at least one of a state of pre-runtime contents, including but not limited to initialization or readiness, base and limit addresses or table lookaside buffer mapping contents of said memory subsystem.

11. The computer system of claim 1 wherein said current state of said memory subsystem comprises at least one of a state of non-runtime contents, including but not limited to environmental conditions, serial number, security keys, selftest results, power cycles, hour meter or firmware revisions of said memory subsystem.

12. The computer system of claims 1 wherein said current state of said memory subsystem comprises runtime contents, of said memory subsystem used for billing customers in a configurable cloud processing environment.

13. The computer system of claim 12 wherein said memory elements comprise a NAND Flash, and said runtime content includes excessive writes to said NAND Flash.

14. The computer system of claim 1 wherein said current state of said memory subsystem and an associated subsystem status information block includes a backup power source or persistent memory device which back up data when the subsystem is hot swapped.

15. The computer system of claim 1 wherein said current state of said memory subsystem and an associated subsystem status information block includes a backup power source or persistent memory device which back up data when the subsystem is powered down and relocated to a mobile device.

16. The computer system of claim 1 wherein said current state of said memory subsystem and an associated subsystem status information block includes an auxiliary port for direct communication with a duplicate local or remote subsystem when used in a redundant fashion.

17. The computer system of claim 1 wherein said current state of said memory subsystem and an associated subsystem status information block includes an auxiliary port for direct communication when information is transferred to a mobile device.

18. A method of processing information in a reconfigurable computing system having a reconfigurable processor comprising a memory subsystem query controller and a reconfigurable memory controller, a memory subsystem comprising a plurality of memory storage elements and an associated subsystem status information block, the method comprising:

during processing of a first task by the reconfigurable processor, the memory controller transmitting status information to the memory subsystem and the subsystem status information block maintaining data received from the memory controller;

upon completion of the first task, the memory subsystem maintaining memory status information indicative of a memory status;

reconfiguring the reconfigurable processor to carry out a second task; and

upon reconfiguration, the reconfigurable processor querying the memory subsystem to provide memory status information, wherein the memory status information can then be used to complete the second task.

19. The method of claim 17 wherein said status information comprises a confirmation that said memory is initialized, and an address identifying information needed for said second task.

20. The method of claim 17 wherein said status information comprises a processor table map.

21. The method of claim 17 wherein said status information comprises an address pointer indicative of a location containing a data set produced by said first task.

22. The method of claim 21 wherein said second task can locate and use said data set produced by said first task.