Memory transaction with reduced latency

Information

  • Patent Grant
  • 10120586
  • Patent Number
    10,120,586
  • Date Filed
    Saturday, February 7, 2015
    9 years ago
  • Date Issued
    Tuesday, November 6, 2018
    6 years ago
Abstract
A solution for performing reduced latency memory read transactions is disclosed. In one example, a storage apparatus has a memory array that includes: a flash device having a data register, a memory interface coupled to the memory array and a buffer set that includes at least one buffer suitable for use as a prefetch buffer. The memory interface, in response to a memory read transaction request, performs a read operation and, if stored data exists within the memory array that meets a prefetch selection criterion, also performs an internal read operation. The internal read operation includes allocating a prefetch buffer in the buffer set and storing the data as prefetch data in the prefetch buffer. If the memory interface receives a second memory read transaction request for data that is currently available as prefetch data, the memory interface responds by performing a forwarding transaction that includes retrieving the prefetch data from the prefetch buffer and forwarding the prefetch data to a host.
Description
FIELD OF INVENTION

The present invention relates to solutions for achieving reduced latency memory read transactions in storage or memory devices. More particularly, these solutions achieve reduced latency memory read transactions by allocating a prefetch buffer from a set of buffers that includes at least one buffer, such as a data register, from a flash device.


BACKGROUND

The relentless increase in Internet usage and e-commerce as well as the proliferation of networked digital computing devices has driven the demand for not only large capacity data storage but also high data availability and sophisticated data management, such as storage virtualization. To meet these needs, many vendors offer networked attached storage (NAS) devices, storage array network (SAN) devices and sophisticated servers that have directly attached arrays of mass storage. These solutions can provide users with managed access to their data directly from their computing device or through a network and with high data availability. These solutions are not without challenges, however.


One challenge includes reducing latency in memory read transactions. For example, in enterprise database applications or in on-line transaction processing, massive amounts of data may need to be sorted or filtered. This requires that these applications have access to storage devices that can not only provide large data capacity but perform low latency memory read transactions for data stored randomly in the storage devices. Another example includes on-demand video applications. These applications must have access to storage devices that can retrieve large amounts of sequential data, such as video, with low latency and in multiple streams in order to maximize viewing enjoyment of the video in real-time by multiple end-users.


Yet another example requiring reduced latency in memory read transactions includes a storage virtualization application that can aggregate a pool of storage that can be used by requesting hosts. This pool of storage may include a set of storage devices that may be interconnected through a LAN, WAN or both, and that may use mass storage devices that have relatively high memory transaction read latency, such as hard disk drives (HDD), or that are coupled to a network with a relatively low network bandwidth.


Consequently, a need exists for a storage device that can provide low latency memory read transactions in a variety of applications.


SUMMARY

A solution for performing reduced latency memory read transactions is disclosed. In one example, this solution may include a storage apparatus having a memory array that includes: a flash device having a data register, a memory interface coupled to the memory array and a buffer set that includes at least one buffer that is suitable for use as a prefetch buffer. The buffer set, where one buffer in the buffer set includes a data register, is coupled to the memory interface. The memory interface, in response to a memory read transaction request, performs a read operation and, if stored data exists within the memory array that meets at least one prefetch selection criterion, also performs an internal read operation. The internal read operation includes allocating a prefetch buffer in the buffer set and storing the data as prefetch data in the prefetch buffer. If the memory interface receives a second memory read transaction request for data and if the data is currently available as prefetch data in the prefetch buffer, the memory interface responds by performing a forwarding transaction that includes retrieving the prefetch data from the prefetch buffer and forwarding the prefetch data to a host.





BRIEF DESCRIPTION OF DRAWINGS


FIG. 1 is a block diagram of a reduced latency storage apparatus in accordance with a first embodiment of the present invention.



FIG. 2 is a block diagram of a reduced latency memory interface for use in a storage apparatus in accordance with a second embodiment of the present invention.



FIG. 3 is a block diagram of a reduced latency memory interface for use in a storage apparatus in accordance with a third embodiment of the present invention.



FIG. 4 illustrates a method for using a reduced latency memory interface in a storage apparatus in accordance with a fourth embodiment of the present invention.





DETAILED DESCRIPTION OF THE INVENTION

While the invention has been described in conjunction with a specific best mode, it is to be understood that many alternatives, modifications, and variations will be apparent to those skilled in the art in light of the following description. Those skilled in the art would recognize after reviewing this application that the embodiments disclosed, including embodiments directed to methods or processes, can be implemented using various types of integrated circuits, including microprocessors, programmable logic arrays, such as FPGAs, discrete active and passive devices, such as logic gates and logic functions, or any combination of these devices. The use of these devices in the embodiments of the invention shown below would not require undue experimentation or further invention. In addition, for clarity purposes, not all of the routine features of the embodiments described herein are shown or described. It is appreciated that in the development of any such actual implementation, numerous implementation-specific decisions must be made to achieve the developer's specific goals. These specific goals will vary from one implementation to another and from one developer to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming but would nevertheless be a routine engineering undertaking for those of ordinary skill in the art having the benefit of this disclosure.


Various embodiments of the present invention disclosed herein pertain to achieving reduced memory transaction read latency in a memory device, such as a storage apparatus that employs a memory interface coupled to a memory array. Reduced read latency may be achieved in such a storage apparatus by allocating a buffer from a set of at least one buffer, such as a data register included in a flash device, and by using this allocated buffer to store prefetch data. The number of buffers allocated as prefetch buffers for storing prefetch data may be selected at the time of manufacture, at the time of boot-up or dynamically as needed by the storage apparatus. In this example, this flash device comprises at least a portion of the memory array.


Referring now to FIG. 1, reduced memory read transaction latency may be achieved by using a storage apparatus 10 that includes a memory interface 24 coupled via a memory bus 22-1 to a memory array 26. Memory array 26 includes at least one flash device, such as flash devices 14-1 through 14-n, where n may be any number greater than zero (0). The flash devices may include data registers. For example, flash devices 14-1 and 14-n may respectively include data registers 16-1 through 16-n. The data registers form part of buffer set 28. The term “flash device” is intended to include any form of non-volatile memory that includes a set of non-volatile memory cells, including multi-level memory cells. This flash device permits read and write operations to be performed on these memory cells according to a protocol supported by the flash device. This flash device may be implemented using a flash memory device that complies with the Open NAND Flash Interface Specification, commonly referred to as ONFI Specification. The term “ONFI Specification” is a known device interface standard created by a consortium of technology companies, called the “ONFI Workgroup”. The ONFI Workgroup develops open standards for NAND flash memory devices and for devices that communicate with these NAND flash memory devices. The ONFI Workgroup is headquartered in Hillsboro, Oreg. Using a flash device that complies with the ONFI Specification is not intended to limit the embodiment disclosed. One of ordinary skill in the art having the benefit of this disclosure would readily recognize that other types of flash devices employing different device interface protocols may be used, such as protocols compatible with the standards created through the Non-Volatile Memory Host Controller Interface (“NVMHCI”) working group. Members of the NVMHCI working group include Intel Corporation of Santa Clara, Calif., Dell Inc. of Round Rock, Tex. and Microsoft Corporation of Redmond, Wash.


Memory interface 24 responds to a memory read transaction request 12 received via bus 20 from host 18-1 by performing on memory array 26 a memory operation that corresponds to the transaction requested by host 18-1. For example, if memory interface 24 receives memory read transaction request 12, memory interface 24 performs a read operation on memory array 26 and returns the result of the read operation, such as read data, along bus 20 to host 18-1. Data returned as a result of the read operation is hereinafter called “read data”. Memory interface 24 may also perform an internal read operation if data exists in memory array 26 that meets at least one prefetch selection criterion. This prefetch selection criterion may include a relationship between read data, and a data portion existing in memory array 26, named “stored data”. The type of relationship between read data and stored data is not intended to be limiting in any way. Any type of relationship may be used that increases the likelihood that the stored data selected for prefetching will be later requested by a host coupled to a memory interface 24, such as host 18-1. For example, this prefetch selection criterion may be met if stored data exists that has a memory address that differs from the read data within a selected memory address range. In another example, memory interface 24 determines whether the prefetch selection criterion is met by determining whether any stored data exists in memory array 26 that has a memory address within the same page as a memory address associated with the read data.


The term “host”, such as host 18-1 shown in this embodiment, means any device that has the ability to transmit a memory read transaction request to storage apparatus 10. For example, this may include host 18-1 that can generate a memory read transaction request 12 and that can receive a response resulting from the processing of memory read transaction request 12 by memory interface 24. Memory interface 24 may process memory transactions from more than one requesting device, such as host 18-1 through host 18-n. For example, as shown in FIG. 1, host 18-1 may generate a memory read transaction request 12, while another host 18-n may receive a response, such as prefetch data 30, that is a result of another subsequent memory read transaction request 32 sent by host 18-n.


The term “data portion” is intended to refer to any data size granularity used by storage apparatus 10 to address data stored in memory array 26. For example, data may be addressed in increments that may include a flash page, flash block, a file or the like.


If memory interface 24 determines the prefetch selection criterion is met, it initiates an internal read operation. This internal read operation includes memory interface 24 retrieving data that meets the prefetch selection criterion from memory array 26. Memory interface 24 may perform this internal read operation without host prompting. However, if memory interface 24 determines the prefetch selection criterion has not been met, memory interface 24 does not perform this internal read operation. Data retrieved from memory array 26 that meets the prefetch selection criterion is hereinafter called “prefetch data”.


As part of the internal read operation, memory interface 24 allocates at least one buffer from buffer set 28 to store prefetch data 30. The number of buffers allocated by memory interface 24 as prefetch buffers for storing prefetch data may be selected at the time of manufacture, at the time of initialization or dynamically as needed by the storage apparatus. In one implementation, the number of buffers allocated as prefetch buffers may be initially selected by memory interface 24. Memory interface 24 may then dynamically adjust the number of buffers after initialization, depending on an amount of storage needed for data treated as prefetch data during the processing of memory read transaction requests. For example in FIG. 1, memory interface 24 may allocate data register 16-1 as a storage space suitable for storing prefetch data 30. This action may render non-allocated buffers, such as data registers 16-n in buffer set 28, available to storage apparatus 10 for other memory uses as needed. Buffers allocated for storing prefetch data, such as buffer 16-1 are hereinafter called “prefetch buffers”. Storing prefetch data 30 in a prefetch buffer, such as prefetch buffer 17, renders prefetch data 30 readily available to a requesting host if requested by the host, such as through a subsequent memory read transaction request.


Allocation of a prefetch buffer in the above manner is not to be taken as a limitation in any way. One of ordinary skill in the art having the benefit of this disclosure may use other techniques or procedures to allocate a buffer as a prefetch buffer for storing prefetch data. For example, memory array 26 may further include at least one HDD, which is not shown to avoid overcomplicating this disclosure. During initialization, memory interface 24 operating under program control may by default prefetch data from random areas in this HDD. This configuration option may be preferable when low latency performance during random access is required, such as in database applications. Another option may include configuring memory interface 24 through program code to provide an option in the form of a vendor-specific interface command to allow a host, such as host 18-1, to select the prefetching method to be used by memory interface 24 during initialization. For instance, if storage apparatus 10 will be used to store large files that tend to be stored sequentially, such as video files, memory interface 24 may be configured to prefetch sequential data rather than random data. To reduce initialization time of storage apparatus 10, these prefetching options during initialization may be disabled. In another possible configuration, storage apparatus 10 may support a host-controlled non-volatile cache command set. This allows a host, such as host 18-1, to keep selected data in low latency non-volatile memory that may form a portion of memory array 26, such as flash devices 14-1 through 14-n, rendering this selected data to be available as prefetch data during initialization. During initialization, memory interface 24 operating under the program control detects this selected data and automatically prefetches this data by storing the data in a prefetch buffer.


If memory interface 24 receives memory read transaction request 32, which may be subsequent to memory read transaction request 12, and the data requested by memory read transaction request 32 is currently available in prefetch buffer 17 as prefetch data 30, memory interface 24 will initiate a forwarding transaction, reducing the read latency of the memory read transaction resulting from memory read transaction request 32. This forwarding transaction includes retrieving the prefetch data previously stored in a prefetch buffer, such as prefetch data 30 and prefetch buffer 17, respectively, and forwarding prefetch data 30 to the requesting host, such as host 18-n.


Storage apparatus 10 also includes a data transmission conduit, such as a memory bus 22-1, for coupling memory interface 24 and memory array 26. Memory interface 24 uses memory bus 22-1 as a conduit for transferring data between memory interface 24 and memory array 26. Memory bus 22-1 may include additional memory bus 22-n, where n may be any number greater than zero. Additional memory buses, such as memory bus 22-n, may be implemented to accompany an expansion of memory array 26. Memory bus 22-1 though 22-n are provided as one possible implementation feature and are not intended to be limiting in any way. Bus 20 may be used to couple host 18-1 to storage apparatus 10. Additional buses, such as bus 20-n, may be implemented to enable additional hosts, such as host 18-n, to communicate with memory interface 24.



FIG. 2 illustrates another embodiment of a storage apparatus 34 that supports prefetching transactions and that employs a reduced latency memory interface 48. Storage apparatus 34 includes a memory array 50, which is coupled to memory interface 48 via a memory bus 46. Memory interface 48 is responsive to a memory read transaction request 36 sent via bus 44 from a host 42, and enables storage apparatus 34 to perform reduced latency memory transactions in response to receiving second memory read transaction request 64. In this embodiment, memory interface 48 includes a DMA controller 56 and flash memory controller 60. Buffer set 52 includes data registers 40-1 to 40-n from flash devices 38-1 through 38-n, respectively; at least one buffer from DMA controller 56, such as buffer 58; at least one buffer from flash memory controller 60, such as buffer 62; or any combination of these data registers and buffers. As previously described, a prefetch buffer is a data store that has been allocated to store prefetch data.


The number of buffers allocated as prefetch buffers may be selected at the time of manufacture, during initialization or during the processing of memory operations. In one example, memory interface 48 may initially allocate a selected number of buffers at the time of initialization, and then dynamically adjust the number of buffers allocated as prefetch buffers after initialization, depending on an amount of storage needed for data treated as prefetch data during the processing of memory read transaction requests. This example is not intended to limit the various embodiments disclosed herein. Other embodiments for allocating a selected number of buffers that may be applicable to the example shown in FIG. 2 have been previously disclosed in FIG. 1. In addition, the number of buffers allocated as prefetch buffers may depend on an amount of storage needed for the prefetch data. For instance, memory interface 48 may allocate data register 40-1 and buffer 58 as storage space suitable for storing prefetch data 44. This action may also render non-allocated buffers, such as data registers 40-n and buffer 62 in buffer set 52 available to storage apparatus 34 for other memory uses as needed. Buffers allocated for storing prefetch data, such as buffer 58 and data register 40-1 are hereinafter called “prefetch buffers”.


Memory array 50, host 42-1 through 42-n, flash devices 38-1 through 38-n, bus 46-1 through 46-n, memory read transaction request 36, second memory read transaction request 64 and memory bus 46-1 through 46-n may be implemented to have substantially the same function and structure as memory array 26, host 18-1 through 18-n, flash devices 16-1 though 16-n, bus 20 through 20-n, memory read transaction request 12, second memory read transaction request 32 and memory bus 22-1 through 22-n respectively, disclosed above with respect to FIG. 1.


In this embodiment, buffer set 52 includes buffer 58 and buffer 62. Like data registers 40-1 through 40-n, buffers 58 and 62 form part of buffer set 52 and can be used as prefetch buffers if memory interface 48 allocates these buffers as prefetch buffers. Otherwise, memory interface 24 in FIG. 1 is similar to memory interface 48 in function. For example, when prefetch data 44 is found during an internal read operation, memory interface 48 stores prefetch data 44 into prefetch buffer 35, such as buffer 58 and data register 40-1. Also, if memory interface 48 receives a second memory read transaction request 64, which may be subsequent to the earlier memory read transaction request 36, for data and this data has been previously stored as prefetch data, such as prefetch data 54, and prefetch data 54 is stored in prefetch buffer 35, memory interface 48 initiates a forwarding transaction. This forwarding transaction is similar to the forwarding transaction described earlier with respect to the embodiment corresponding to FIG. 1, above. However, unlike the forwarding transaction described in with respect to FIG. 1 which only shows data registers which may be allocated as prefetch buffers, the forwarding transaction here may include obtaining prefetch data from any of the buffers in buffer set 52 if memory interface 48 allocates those buffers as prefetch buffers.


For example, if the data requested in the second memory read transaction 64 has been stored as prefetch data 44, and prefetch data 44 is stored in buffer 58, the forwarding transaction includes retrieving prefetch data 44 from buffer 58 and forwarding prefetch data 44 to the host that sent the second memory read transaction request. In another example, if the data requested in the second memory read transaction request 64 is stored as prefetch data 44, and prefetch data 44 is stored in data register 40-1, the forwarding transaction includes retrieving prefetch data 44 from data register 40-1 and forwarding prefetch data 44 to the host that sent the second memory read transaction request. Thus, memory interface 48 may perform an internal read operation and forwarding transaction using any of the buffers, such as data registers 40-1 through 40-n, buffer 58, and buffer 62 that memory interface 48 has allocated as prefetch buffers.



FIG. 3 illustrates another embodiment of a storage apparatus 66 that supports prefetching transactions and that employs a reduced latency memory interface 80 in accordance with another embodiment of the present invention. Storage apparatus 66 includes a memory array 82 coupled to a memory interface 80 via a memory bus 98. Memory interface 80 is responsive to a memory read transaction request 68 sent via bus 78 from a host 76-1 by enabling storage apparatus 66 to perform a reduced latency memory transaction in response to receiving a second memory read transaction request 106.


Memory interface 80 includes a DMA controller 88, flash memory controller 92, system bus 96, local memory 100, host interface 102 and local processor 104. Host interface 102 allows at least one device, such as host 76-1, to communicate with devices within storage apparatus 66. These devices may include local processor 104, local memory 100 and DMA controller 88 of memory interface 80. For example, memory read transaction request 68 may be received by memory interface 80 through host interface 102, permitting memory interface 80 to process this request as disclosed herein. System bus 96 is a conduit for transferring data between DMA controller 88, local processor 104, local memory 100 and host interface 102. Local processor 104, host interface 102 and DMA controller 88 may access local memory 100 via system bus 96 as needed. Local memory 100 may be implemented using any form of memory, such as various types of DRAM, non-volatile memory and the like.


Memory array 82 includes at least one flash device, such as flash devices 70-1 through 70-n, where n may be any number greater than zero (0). Each flash device may include flash pages and data registers. For example, flash devices 70-1 and 70-n may each respectively include flash pages 74-0 through 74-n, flash pages 75-0 through 75-n, and data registers 72-1 through 72-n. In this embodiment, data registers form part of buffer set 84. Memory array 82, host 76-1 through 76-n, bus 78 through 78-n, buffer set 84, memory read transaction request 68, second memory read transaction request 106 and memory bus 98-1 through 98-n may be respectively implemented to have substantially the same function and structure as memory array 50, host 42-1 though 42-n, bus 54 through 54-n, buffer set 52, memory read transaction request 36, second memory read transaction request 64 and memory bus 46-1 though 46-n respectively, disclosed above with respect to FIG. 2.


Host 76-1 sends memory read transaction request 68 to storage apparatus 66 for data located in memory array 82. Operating under program control, local processor 104 analyzes and responds to memory read transaction request 68 by generating DMA instructions that will cause DMA controller 88 to read this data from memory array 82 through memory controller 92. If this data is available, memory interface 92 retrieves this data, which is transferred to local memory by DMA controller 88, and eventually transferred to host 76-1 via host interface 102. Data obtained during this memory read transaction request is hereinafter named “read data”.


Local processor 104 also identifies “prefetch data”. Prefetch data is any data currently stored in memory array 82 that meets a prefetch selection criterion. This prefetch selection criterion may include a relationship between the read data and any stored data. For example, this prefetch selection criterion may be met if stored data exists that has a memory address within a selected memory address range from the memory address of the read data. In another example, memory interface 80 determines whether this prefetch selection criterion is met by determining whether any stored data exists in memory array 82 that has a memory address within the same page as a memory address associated with the read data. The type of relationship between read data and stored data is not intended to be limiting in any way. Any type of relationship may be used that increases the likelihood that the stored data selected for prefetching will be later requested by a host coupled to a memory interface 80, such as host 76-1.


Local processor 104 may also perform an additional read operation, called an internal read operation. This internal read operation is a process executed by the local processor 104 to retrieve prefetch data 86 from memory array 82. This internal read operation includes local processor 104 sending an instruction, such as instruction 122, to DMA controller 88 to retrieve prefetch data 86 from memory array 82. For example, if memory array 82 addresses stored data by flash page, instruction 122 contains the address of the specific flash page within a flash device that holds prefetch data 86, such as flash page 74-0 and flash device 70-1, respectively. Instruction 122 also causes DMA controller 88 to retrieve prefetch data 86 from the flash page and flash device identified by the address mentioned above.


When DMA controller 88 receives instruction 122, instruction 122 causes DMA controller 88 to use flash memory controller 92 to cause flash device 70-1 to transfer prefetch data 86. The internal read operation also includes local processor 104 allocating a buffer in buffer set 84 to store prefetch data 86. Allocating a buffer as a prefetch buffer may be performed statically, such as at the time of manufacture, dynamically by local processor 104 or both. In one implementation, the number of buffers allocated as prefetch buffers depends on an amount of storage needed for the prefetch data. For example, in FIG. 3, memory interface 84 may allocate data register 72-1 and buffer 90 as storage space suitable for storing prefetch data 86. This action may also render non-allocated buffers, such as data registers 72-n and buffer 94 in buffer set 84 available to storage apparatus 66 for other memory uses. Buffers allocated for storing prefetch data, such as buffer 90 and data register 72-n, are hereinafter called “prefetch buffers”. If a host, such as host 76-1, issues a second memory read transaction request 106 for data and this data has been previously stored as prefetch data in a prefetch buffer such as prefetch data 86 in prefetch buffer 89, local processor 104 responds by retrieving prefetch data 86 from prefetch buffer 89 and by placing prefetch data 86 into local memory 100. When local processor 104 determines local memory 100 contains prefetch data 86, local processor 104 forwards prefetch data 86 from local memory 100 to host interface 102, which in turn transfers the prefetch data to host 76-1. One of ordinary skill in the art having the benefit of this disclosure would readily recognize that rather than using local memory to store prefetch data, prefetch data may be sent directly to the host or processed in any other manner envisioned by a user.



FIG. 4 discloses a method for reducing latency in memory read transactions in accordance with another embodiment of the present invention. This method may be performed by using a reduced latency memory interface that is coupled to a memory array that includes a flash device and also coupled to a buffer set that includes a buffer. These elements may be provided in a storage apparatus, such as storage apparatus 10, 34, or 66 in FIGS. 1 through 3, respectively.


Under the method shown, a memory read transaction request is received 108. For example, as shown in FIG. 3, a host 76-1 may send a memory read transaction request 68 to storage apparatus 66, which uses host interface 102 to receive memory read transaction request 68. A read operation is then performed 110. This read operation may be performed by memory interface 80 by obtaining read data requested by host 76-1 from memory array 82. For example, in FIG. 3, memory array 24 responds to memory read transaction request 12 and obtains read data from memory array 26, returning read data to host 18-1 if this data is available.


Local processor 104 identifies 112 data currently stored in memory array 82 that meets a prefetch selection criterion. For example, in FIG. 3, if local processor 104 identifies stored data in memory array 82 that are within a selected address range of the address range of the read data.


If prefetch data is identified, an internal read operation is performed 114. For example, in FIG. 3, memory interface 80 causes a flash device in memory array 82 that holds this prefetch data, such as prefetch data 86, to transfer the prefetch data 86 from a flash page storing the prefetch data. Additionally, the internal read operation includes local processor 104 allocating a buffer as a prefetch buffer in buffer set 84 for storing prefetch data 86. The internal read operation further includes storing prefetch data 86 in a prefetch buffer, such as prefetch buffer 89.


If a second memory read transaction request is received for data and that data is stored as prefetch data in a prefetch buffer, a forwarding transaction is performed 120. For example, referring to FIG. 3, if a second memory read transaction request 106 is received for data and that data is stored as prefetch data 86 in prefetch buffer 89, local processor 104 responds to memory read transaction request 106 and retrieves prefetch data 86 from prefetch buffer 89. Local processor 104 forwards prefetch data 86 from prefetch buffer 89 to local memory 100. Local processor 104 forwards prefetch data 86 from local memory 100 to host 76-1. This transfer of prefetch data 86 from buffer set 84 to local memory 100 is not depicted in FIG. 3 to avoid overcomplicating this herein disclosure. In this example, flash devices 14-1 through 14-n function as mass storage devices. However, in another embodiment (not shown), these flash devices may function as a cache to another type of storage device, such as a set of HDDs arranged in a RAID, JBOD or other configuration. This set of HDDs is not shown in the drawings to avoid overcomplicating the herein disclosure, but may be included as part of the memory array, such as memory array 82 in FIG. 4.


While the present invention has been described in particular embodiments, it should be appreciated that the present invention should not be construed as limited by such embodiments. Rather, the present invention should be construed according to the claims below.

Claims
  • 1. A storage apparatus for performing reduced memory read transactions, said storage apparatus responsive to memory transaction requests from at least one host, the storage apparatus comprising: a memory array comprising a plurality of flash memory devices, said plurality of flash memory devices includes a first flash memory device, said first flash memory device including a data register and non-volatile memory cells;a memory interface coupled to said memory array, wherein said memory interface comprises a local processor, a Direct Memory Access (DMA) controller and a flash memory controller, and wherein said DMA controller comprises a first buffer and wherein said flash memory controller comprises a second buffer;a buffer set that includes a plurality of buffers that are suitable for use as prefetch buffers, at least some of said buffer set included in said memory interface;said buffer set comprising said first buffer in said DMA controller in said memory interface, said second buffer in said flash memory controller, and said data register in said first flash memory device such that said first buffer, said second buffer, and said data register are used as said prefetch buffers;wherein said memory interface allocates said prefetch buffers in said buffer set, said prefetch buffers including said first buffer in said DMA controller, said second buffer in said flash memory controller, and said data register so that said buffer set includes said prefetch buffers allocated for storing prefetch data and at least one non-allocated buffer that is available to said storage apparatus for other memory uses;wherein said memory interface is configured to identify stored data that meets a prefetch selection criterion and wherein said stored data are stored in said memory array;wherein, in response to receiving a memory read transaction request, said memory interface performs a read operation wherein said DMA controller reads said stored data from said memory array through said flash memory controller and, if said memory interface identifies said stored data that meets said prefetch selection criterion in said memory array, said memory interface performs an internal read operation that includes allocating said prefetch buffers in said buffer set and storing said stored data in at least one of said prefetch buffers as said prefetch data; andwherein, if said memory interface receives a second memory read transaction request for read data and if said read data is currently available as said prefetch data in at least one of said prefetch buffers, said memory interface responds to said second memory read transaction request by performing a forwarding transaction that includes said local processor retrieving said prefetch data from at least one of said prefetch buffers and said local processor forwarding said prefetch data to said host, reducing read latency of said second memory read transaction request.
  • 2. The storage apparatus of claim 1, wherein said DMA controller reads data from said first flash memory device in said memory array through said flash memory controller.
  • 3. The storage apparatus of claim 1, wherein said memory interface further includes a host interface for receiving said memory read transaction request from said host.
  • 4. The storage apparatus of claim 1, wherein said DMA controller uses said flash memory controller to transfer said prefetch data from said memory array.
  • 5. The storage apparatus of claim 1, wherein said buffer set comprises said first buffer which comprises a first fixed buffer from said DMA controller.
  • 6. The storage apparatus of claim 1, wherein said buffer set includes a second fixed buffer from said flash memory controller.
  • 7. The storage apparatus of claim 1, wherein said first flash memory device contains at least one flash page.
  • 8. The storage apparatus of claim 1, wherein said storage apparatus includes a memory bus for coupling said memory array to said memory interface.
  • 9. The storage apparatus of claim 1, wherein said storage apparatus includes a bus for receiving said memory read transaction request from said host and sending data from the storage apparatus to said host.
  • 10. The storage apparatus of claim 1, wherein said storage apparatus includes a system bus for receiving and sending data between said local processor, said DMA controller, a local memory, and a host interface.
  • 11. The storage apparatus of claim 1 wherein said memory interface includes said DMA controller, said local processor, a host interface and a local memory coupled together through a system bus; and said memory interface further includes said flash memory controller coupled to said DMA controller and to said memory array through a memory bus.
  • 12. The storage apparatus of claim 1, wherein said buffer set includes another data register in another flash memory device in said memory array.
  • 13. A method for reducing latency in memory read transactions, the method comprising: using a low latency memory interface coupled to a memory array comprising a plurality of flash memory devices, said plurality of flash memory devices includes a first flash memory device, said first flash memory device includes a data register and non-volatile memory cells;wherein said memory interface comprises a buffer set that includes a plurality of buffers that are suitable for use as prefetch buffers, wherein said memory interface comprises a local processor, a Direct Memory Access (DMA) controller and a flash memory controller, and wherein said DMA controller comprises a first buffer and wherein said flash memory controller comprises a second buffer;wherein said buffer set comprises said first buffer, said second buffer, and said data register such that said first buffer, said second buffer, and said data register are used as said prefetch buffers;allocating, by said memory interface, said prefetch buffers in said buffer set, said prefetch buffers including said first buffer in said DMA controller, said second buffer in said flash memory controller, and said data register so that said buffer set includes said prefetch buffers allocated for storing prefetch data and at least one non-allocated buffer that is available to said memory interface for other memory uses; andwherein said memory interface responds to memory read transaction requests from a host, the method further comprising: receiving, by said memory interface, a memory read transaction request;performing a read operation in response to said memory read transaction request wherein said DMA controller reads stored data from said memory array through said flash memory controller;identifying, by said memory interface, said stored data that meets a prefetch selection criterion, wherein said stored data are stored in said memory array;if said memory interface identifies said stored data that meets said prefetch selection criterion in said memory array, then performing an internal read operation that includes allocating said prefetch buffers in said buffer set and storing said stored data in at least one of said prefetch buffers as said prefetch data; andif said memory interface receives a second memory read transaction request for read data and if said read data is currently available as said prefetch data in at least one of said prefetch buffers, then performing a forwarding transaction that includes said local processor retrieving said prefetch data from at least one of said prefetch buffers and said local processor forwarding said prefetch data to said host.
  • 14. The method of claim 13 wherein said prefetching selection criterion is met if said prefetch data is associated with a memory address within a same page as a memory address associated with said read data.
  • 15. The method of claim 13 wherein said prefetch selection criterion is met if said prefetch data is associated with a memory address within a same flash memory device as a memory address associated with data read during a response to said memory read transaction request.
  • 16. The method of claim 13 wherein said prefetch selection criterion is met if a memory address of said prefetch data differs within a selected memory address range from a memory address of data read during a response to said memory read transaction request.
  • 17. The method of claim 13 wherein a response to said second memory read transaction request includes transferring said prefetch data from at least one of said prefetch buffers to a local memory.
  • 18. The method of claim 17 wherein a response to said second memory read transaction request includes forwarding said prefetch data from said local memory to said host.
  • 19. An article of manufacture, comprising: a non-transitory computer-readable medium having stored thereon instructions operable to permit an apparatus to perform a method comprising: receiving, by a memory interface, a memory read transaction request from a host;wherein said memory interface is coupled to a memory array comprising a plurality of flash memory devices, said plurality of flash memory devices includes a first flash memory device, wherein said first flash memory device comprises a data register and non-volatile memory cells;wherein said memory interface comprises a buffer set that includes a plurality of buffers that are suitable for use as prefetch buffers;wherein said memory interface comprises a local processor, a Direct Memory Access (DMA) controller and a flash memory controller, and wherein said DMA controller comprises a first buffer and wherein said flash memory controller comprises a second buffer;wherein said buffer set comprises said first buffer, said second buffer, and said data register such that said first buffer, said second buffer, and said data register are used as said prefetch buffers;allocating, by said memory interface, said prefetch buffers in said buffer set, said prefetch buffers including said first buffer in said DMA controller, said second buffer in said flash memory controller, and said data register so that said buffer set includes said prefetch buffers allocated for storing prefetch data and at least one non-allocated buffer that is available to said memory interface for other memory uses;performing a read operation in response to said memory read transaction request wherein said DMA controller reads stored data from said memory array through said flash memory controller;identifying, by said memory interface, said stored data that meets a prefetch selection criterion, wherein said stored data are stored in said memory array;performing an internal read operation that includes allocating said prefetch buffers in said buffer set and storing said stored data in at least one of said prefetch buffers as said prefetch data if said memory interface identifies said stored data that meets said prefetch selection criterion in said memory array; andperforming a forwarding transaction that includes said local processor retrieving said prefetch data from at least one of said prefetch buffers and said local processor forwarding said prefetch data to said host if said memory interface receives a second memory read transaction request for read data and if said read data is currently available as said prefetch data in at least one of said prefetch buffers.
  • 20. The article of manufacture of claim 19, wherein said DMA controller reads data from said first flash memory device in said memory array through said flash memory controller.
  • 21. A storage apparatus for performing reduced latency memory read transactions, the storage apparatus comprising: a memory array including a plurality of non-volatile memory devices;a memory interface coupled by a memory bus to the memory array and responsive to memory read transaction requests;the memory interface coupled by a bus to a host during a transmission of memory transaction requests from the host to the memory interface;the memory interface including a Direct Memory Access (DMA) controller comprising a first buffer and a flash memory controller comprising a second buffer; andwherein the memory interface allocates a plurality of prefetch buffers in a buffer set, the plurality of prefetch buffers including the first buffer in the DMA controller and the second buffer in the flash memory controller so that the buffer set includes the plurality of prefetch buffers allocated for storing prefetch data and one or more non-allocated buffers available to the storage apparatus for other memory uses;the memory interface configured to perform a read operation on the memory array in response to a memory read transaction request and configured to perform an internal read operation if the memory interface identifies stored data, in the memory array, meeting a prefetch selection criterion;the internal read operation comprising the memory interface allocating a data store in the buffer set and storing the stored data in the data store as the prefetch data available to a second memory read transaction.
  • 22. A method of performing reduced latency memory read transactions in a storage apparatus, the method comprising: receiving, by a memory interface, a memory read transaction request from a host and performing, by the memory interface, a read operation on a memory array; andperforming, by the memory interface, an internal read operation if stored data, in the memory array, meets a prefetch selection criterion;wherein performing the internal read operation comprises: allocating a data store in a buffer set and storing the stored data in the data store as a prefetch data;the memory array including a plurality of non-volatile memory devices;the memory interface coupled by a bus to the host during a transmission of memory transaction requests from the host to the memory interface;the memory interface including a Direct Memory Access (DMA) controller comprising a first buffer and a flash memory controller comprising a second buffer;wherein the memory interface, coupled by a memory bus to the memory array, allocates a plurality of prefetch buffers in the buffer set, wherein the plurality of prefetch buffers includes the first buffer in the DMA controller and the second buffer in the flash memory controller so that the buffer set includes the plurality of prefetch buffers allocated for storing the prefetch data available to a second memory read transaction and one or more non-allocated buffers available to the storage apparatus for other memory uses.
  • 23. An article of manufacture, comprising: a non-transitory computer-readable medium having stored thereon instructions operable to permit a storage apparatus to perform a method comprising: receiving, by a memory interface, a memory read transaction request from a host and performing, by the memory interface, a read operation on a memory array; andperforming, by the memory interface, an internal read operation if stored data, in the memory array, meets a prefetch selection criterion;wherein performing the internal read operation comprises: allocating a data store in a buffer set and storing the stored data in the data store as a prefetch data;the memory array including a plurality of non-volatile memory devices;the memory interface coupled by a bus to the host during a transmission of memory transaction requests from the host to the memory interface;the memory interface including a Direct Memory Access (DMA) controller comprising a first buffer and a flash memory controller comprising a second buffer;wherein the memory interface, coupled by a memory bus to the memory array, allocates a plurality of prefetch buffers in the buffer set, wherein the plurality of prefetch buffers includes the first buffer in the DMA controller and the second buffer in the flash memory controller so that the buffer set includes the plurality of prefetch buffers allocated for storing the prefetch data available to a second memory read transaction and one or more non-allocated buffers available to the storage apparatus for other memory uses.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of United States Application, entitled “Reduced Latency Memory Read Transactions In Storage Devices”, having a filing date of 13 Nov. 2008 and Ser. No. 12/270,626, which claims the benefit of and a priority to United States Provisional Application, entitled “Apparatus and Method for Performing Reduced Latency Memory Read Transactions”, having a filing date of 16 Nov. 2007 and Ser. No. 60/988,728. Application Ser. Nos. 12/270,626 and 60/988,728 are hereby fully incorporated herein by reference.

US Referenced Citations (339)
Number Name Date Kind
4402040 Evett Aug 1983 A
4403283 Myntti et al. Sep 1983 A
4752871 Sparks Jun 1988 A
4967344 Scavezze et al. Oct 1990 A
5111058 Martin May 1992 A
RE34100 Hartness Oct 1992 E
5222046 Kreifels et al. Jun 1993 A
5297148 Harari et al. Mar 1994 A
5339404 Vandling, III Aug 1994 A
5341339 Wells Aug 1994 A
5371709 Fisher et al. Dec 1994 A
5379401 Robinson et al. Jan 1995 A
5388083 Assar et al. Feb 1995 A
5396468 Harari et al. Mar 1995 A
5406529 Asano Apr 1995 A
5432748 Hsu et al. Jul 1995 A
5448577 Wells et al. Sep 1995 A
5459850 Clay et al. Oct 1995 A
5479638 Assar et al. Dec 1995 A
5485595 Assar et al. Jan 1996 A
5488711 Hewitt et al. Jan 1996 A
5500826 Hsu et al. Mar 1996 A
5509134 Fandrich et al. Apr 1996 A
5513138 Manabe et al. Apr 1996 A
5524231 Brown Jun 1996 A
5530828 Kaki et al. Jun 1996 A
5535328 Harari et al. Jul 1996 A
5535356 Kim et al. Jul 1996 A
5542042 Manson Jul 1996 A
5542082 Solhjell Jul 1996 A
5548741 Watanabe Aug 1996 A
5559956 Sukegawa Sep 1996 A
5568423 Jou et al. Oct 1996 A
5568439 Harari Oct 1996 A
5572466 Sukegawa Nov 1996 A
5594883 Pricer Jan 1997 A
5602987 Harari et al. Feb 1997 A
5603001 Sukegawa et al. Feb 1997 A
5606529 Honma et al. Feb 1997 A
5606532 Lambrache et al. Feb 1997 A
5619470 Fukumoto Apr 1997 A
5627783 Miyauchi May 1997 A
5640349 Kakinuma et al. Jun 1997 A
5644784 Peek Jul 1997 A
5682509 Kabenjian Oct 1997 A
5737742 Achiwa et al. Apr 1998 A
5765023 Leger et al. Jun 1998 A
5787466 Berliner Jul 1998 A
5796182 Martin Aug 1998 A
5799200 Brant et al. Aug 1998 A
5802554 Caceres et al. Sep 1998 A
5818029 Thomson Oct 1998 A
5819307 Iwamoto et al. Oct 1998 A
5822251 Bruce et al. Oct 1998 A
5864653 Tavallaei et al. Jan 1999 A
5870627 O'Toole et al. Feb 1999 A
5875351 Riley Feb 1999 A
5881264 Kurosawa Mar 1999 A
5913215 Rubinstein et al. Jun 1999 A
5918033 Heeb et al. Jun 1999 A
5930481 Benhase Jul 1999 A
5933849 Srbljic et al. Aug 1999 A
5943421 Grabon Aug 1999 A
5956743 Bruce et al. Sep 1999 A
5978866 Nain Nov 1999 A
5987621 Duso Nov 1999 A
6000006 Bruce et al. Dec 1999 A
6076137 Asnaashari Jun 2000 A
6098119 Surugucchi et al. Aug 2000 A
6128303 Bergantino Oct 2000 A
6138200 Ogilvie Oct 2000 A
6138247 McKay et al. Oct 2000 A
6151641 Herbert Nov 2000 A
6215875 Nohda Apr 2001 B1
6230269 Spies et al. May 2001 B1
6298071 Taylor et al. Oct 2001 B1
6341342 Thompson et al. Jan 2002 B1
6363441 Bentz et al. Mar 2002 B1
6363444 Platko et al. Mar 2002 B1
6397267 Chong, Jr. May 2002 B1
6404772 Beach et al. Jun 2002 B1
6452602 Morein Sep 2002 B1
6496939 Portman et al. Dec 2002 B2
6526506 Lewis Feb 2003 B1
6529416 Bruce et al. Mar 2003 B2
6557095 Henstrom Apr 2003 B1
6574142 Gelke Jun 2003 B2
6601126 Zaidi et al. Jul 2003 B1
6678754 Soulier Jan 2004 B1
6728840 Shatil et al. Apr 2004 B1
6744635 Portman et al. Jun 2004 B2
6785746 Mahmoud et al. Aug 2004 B1
6757845 Bruce Dec 2004 B2
6857076 Klein Feb 2005 B1
6901499 Aasheim et al. May 2005 B2
6961805 Lakhani et al. Nov 2005 B2
6970446 Krischer et al. Nov 2005 B2
6970890 Bruce et al. Nov 2005 B1
6973546 Johnson Dec 2005 B2
6980795 Hermann et al. Dec 2005 B1
7103684 Chen et al. Sep 2006 B2
7174438 Homma et al. Feb 2007 B2
7194766 Noehring et al. Mar 2007 B2
7263006 Aritome Aug 2007 B2
7283629 Kaler et al. Oct 2007 B2
7305548 Pierce et al. Dec 2007 B2
7330954 Nangle Feb 2008 B2
7372962 Fujimoto et al. Jun 2008 B2
7412631 Uddenberg et al. Aug 2008 B2
7415549 Vemula et al. Aug 2008 B2
7424553 Borrelli et al. Sep 2008 B1
7474926 Carr et al. Jan 2009 B1
7478186 Onufryk et al. Jan 2009 B1
7490177 Kao Feb 2009 B2
7496699 Pope et al. Feb 2009 B2
7500063 Zohar et al. Mar 2009 B2
7506098 Arcedera et al. Mar 2009 B2
7613876 Bruce et al. Nov 2009 B2
7620748 Bruce et al. Nov 2009 B1
7620749 Biran et al. Nov 2009 B2
7624239 Bennett et al. Nov 2009 B2
7660941 Lee et al. Feb 2010 B2
7668925 Liao et al. Feb 2010 B1
7676640 Chow Mar 2010 B2
7716389 Bruce et al. May 2010 B1
7719287 Marks et al. May 2010 B2
7729730 Orcine et al. Jun 2010 B2
7743202 Tsai et al. Jun 2010 B2
7765359 Kang et al. Jul 2010 B2
7877639 Hoang Jan 2011 B2
7913073 Choi Mar 2011 B2
7921237 Holland et al. Apr 2011 B1
7934052 Prins et al. Apr 2011 B2
7958295 Liao et al. Jun 2011 B1
7979614 Yang Jul 2011 B1
7996581 Bond et al. Aug 2011 B2
8010740 Arcedera et al. Oct 2011 B2
8032700 Bruce et al. Oct 2011 B2
8156320 Borras Apr 2012 B2
8161223 Chamseddine et al. Apr 2012 B1
8165301 Bruce et al. Apr 2012 B1
8200879 Falik et al. Jun 2012 B1
8219719 Parry et al. Jul 2012 B1
8225022 Caulkins Jul 2012 B2
8341300 Karamcheti Dec 2012 B1
8341311 Szewerenko et al. Dec 2012 B1
8375257 Hong et al. Feb 2013 B2
8447908 Bruce et al. Apr 2013 B2
8489914 Cagno Jul 2013 B2
8510631 Wu et al. Aug 2013 B2
8560804 Bruce et al. Oct 2013 B2
8583868 Belluomini et al. Nov 2013 B2
8677042 Gupta et al. Mar 2014 B2
8707134 Takahashi et al. Apr 2014 B2
8713417 Jo Apr 2014 B2
8762609 Lam et al. Jun 2014 B1
8788725 Bruce et al. Jul 2014 B2
8832371 Uehara et al. Sep 2014 B2
8856392 Myrah et al. Oct 2014 B2
8959307 Bruce et al. Feb 2015 B1
9043669 Bruce et al. May 2015 B1
9099187 Bruce et al. Aug 2015 B2
9135190 Bruce et al. Sep 2015 B1
9147500 Kim et al. Sep 2015 B2
9158661 Blaine et al. Oct 2015 B2
9201790 Keeler Dec 2015 B2
9400617 Ponce et al. Jul 2016 B2
20010010066 Chin et al. Jul 2001 A1
20020011607 Gelke et al. Jan 2002 A1
20020013880 Gappisch et al. Jan 2002 A1
20020073324 Hsu et al. Jun 2002 A1
20020083262 Fukuzumi Jun 2002 A1
20020141244 Bruce et al. Oct 2002 A1
20030065836 Pecone Apr 2003 A1
20030097248 Terashima et al. May 2003 A1
20030120864 Lee et al. Jun 2003 A1
20030126451 Gorobets Jul 2003 A1
20030131201 Khare et al. Jul 2003 A1
20030161355 Falcomato et al. Aug 2003 A1
20030163624 Matsui et al. Aug 2003 A1
20030182576 Morlang et al. Sep 2003 A1
20030188100 Solomon et al. Oct 2003 A1
20030204675 Dover et al. Oct 2003 A1
20030217202 Zilberman et al. Nov 2003 A1
20030223585 Tardo et al. Dec 2003 A1
20040073721 Goff et al. Apr 2004 A1
20040078632 Infante et al. Apr 2004 A1
20040128553 Buer et al. Jul 2004 A1
20040215868 Solomon et al. Oct 2004 A1
20050055481 Chou et al. Mar 2005 A1
20050078016 Neff Apr 2005 A1
20050097368 Peinado et al. May 2005 A1
20050120146 Chen et al. Jun 2005 A1
20050210149 Kimball Sep 2005 A1
20050210159 Voorhees et al. Sep 2005 A1
20050226407 Kasuya et al. Oct 2005 A1
20050240707 Hayashi et al. Oct 2005 A1
20050243610 Guha et al. Nov 2005 A1
20060004957 Hand, III et al. Jan 2006 A1
20060026329 Yu Feb 2006 A1
20060031450 Unrau et al. Feb 2006 A1
20060039406 Day et al. Feb 2006 A1
20060064520 Anand et al. Mar 2006 A1
20060095709 Achiwa May 2006 A1
20060129876 Uemura Jun 2006 A1
20060173970 Pope et al. Aug 2006 A1
20060184723 Sinclair et al. Aug 2006 A1
20070019573 Nishimura Jan 2007 A1
20070028040 Sinclair Feb 2007 A1
20070058478 Murayama Mar 2007 A1
20070073922 Go et al. Mar 2007 A1
20070079017 Brink et al. Apr 2007 A1
20070083680 King et al. Apr 2007 A1
20070088864 Foster Apr 2007 A1
20070093124 Varney et al. Apr 2007 A1
20070094450 VanderWiel Apr 2007 A1
20070096785 Maeda May 2007 A1
20070121499 Pal et al. May 2007 A1
20070130439 Andersson et al. Jun 2007 A1
20070159885 Gorobets Jul 2007 A1
20070174493 Irish et al. Jul 2007 A1
20070174506 Tsuruta Jul 2007 A1
20070195957 Arulambalam et al. Aug 2007 A1
20070288686 Arcedera et al. Dec 2007 A1
20070288692 Bruce et al. Dec 2007 A1
20070294572 Kalwitz et al. Dec 2007 A1
20080005481 Walker Jan 2008 A1
20080052456 Ash et al. Feb 2008 A1
20080052585 LaBerge et al. Feb 2008 A1
20080072031 Choi Mar 2008 A1
20080104264 Duerk et al. May 2008 A1
20080140724 Flynn et al. Jun 2008 A1
20080147963 Tsai et al. Jun 2008 A1
20080189466 Hemmi Aug 2008 A1
20080218230 Shim Sep 2008 A1
20080228959 Wang Sep 2008 A1
20080276037 Chang et al. Nov 2008 A1
20080301256 McWilliams et al. Dec 2008 A1
20090028229 Cagno et al. Jan 2009 A1
20090037565 Andresen et al. Feb 2009 A1
20090055573 Ito Feb 2009 A1
20090077306 Arcedera et al. Mar 2009 A1
20090083022 Nordin et al. Mar 2009 A1
20090094411 Que Apr 2009 A1
20090132620 Arakawa May 2009 A1
20090132752 Poo et al. May 2009 A1
20090150643 Jones et al. Jun 2009 A1
20090158085 Kern et al. Jun 2009 A1
20090172250 Allen et al. Jul 2009 A1
20090172261 Prins et al. Jul 2009 A1
20090172466 Royer et al. Jul 2009 A1
20090240873 Yu et al. Sep 2009 A1
20100058045 Borras et al. Mar 2010 A1
20100095053 Bruce et al. Apr 2010 A1
20100125695 Wu et al. May 2010 A1
20100250806 Devilla et al. Sep 2010 A1
20100268904 Sheffield et al. Oct 2010 A1
20100299538 Miller Nov 2010 A1
20100318706 Kobayashi Dec 2010 A1
20110022778 Schibilla et al. Jan 2011 A1
20110022783 Moshayedi Jan 2011 A1
20110022801 Flynn Jan 2011 A1
20110087833 Jones Apr 2011 A1
20110093648 Belluomini et al. Apr 2011 A1
20110113186 Bruce et al. May 2011 A1
20110133826 Jones et al. Jun 2011 A1
20110145479 Talagala et al. Jun 2011 A1
20110161568 Bruce et al. Jun 2011 A1
20110167204 Estakhri et al. Jul 2011 A1
20110173383 Gorobets Jul 2011 A1
20110197011 Suzuki et al. Aug 2011 A1
20110202709 Rychlik Aug 2011 A1
20110208901 Kim et al. Aug 2011 A1
20110208914 Winokur et al. Aug 2011 A1
20110219150 Piccirillo et al. Sep 2011 A1
20110258405 Asaki et al. Oct 2011 A1
20110264884 Kim Oct 2011 A1
20110264949 Ikeuchi et al. Oct 2011 A1
20120005405 Wu et al. Jan 2012 A1
20120005410 Ikeuchi Jan 2012 A1
20120079352 Frost et al. Mar 2012 A1
20120102263 Aswadhati Apr 2012 A1
20120102268 Smith et al. Apr 2012 A1
20120137050 Wang et al. May 2012 A1
20120159029 Krishnan et al. Jun 2012 A1
20120161568 Umemoto et al. Jun 2012 A1
20120173795 Schuette et al. Jul 2012 A1
20120215973 Cagno et al. Aug 2012 A1
20120249302 Szu Oct 2012 A1
20120260102 Zaks et al. Oct 2012 A1
20120271967 Hirschman Oct 2012 A1
20120303924 Ross Nov 2012 A1
20120311197 Larson et al. Dec 2012 A1
20120324277 Weston-Lewis et al. Dec 2012 A1
20130010058 Pomeroy Jan 2013 A1
20130019053 Somanache et al. Jan 2013 A1
20130073821 Flynn et al. Mar 2013 A1
20130094312 Jan et al. Apr 2013 A1
20130099838 Kim et al. Apr 2013 A1
20130111135 Bell, Jr. et al. May 2013 A1
20130206837 Szu Aug 2013 A1
20130208546 Kim et al. Aug 2013 A1
20130212337 Maruyama Aug 2013 A1
20130212349 Maruyama Aug 2013 A1
20130212425 Blaine et al. Aug 2013 A1
20130246694 Bruce et al. Sep 2013 A1
20130254435 Shapiro et al. Sep 2013 A1
20130262750 Yamasaki et al. Oct 2013 A1
20130282933 Jokinen et al. Oct 2013 A1
20130304775 Davis et al. Nov 2013 A1
20130339578 Ohya et al. Dec 2013 A1
20130339582 Olbrich et al. Dec 2013 A1
20130346672 Sengupta et al. Dec 2013 A1
20140068177 Raghavan Mar 2014 A1
20140095803 Kim et al. Apr 2014 A1
20140104949 Bruce et al. Apr 2014 A1
20140108869 Brewerton et al. Apr 2014 A1
20140189203 Suzuki et al. Jul 2014 A1
20140258788 Maruyama Sep 2014 A1
20140285211 Raffinan Sep 2014 A1
20140331034 Ponce et al. Nov 2014 A1
20150006766 Ponce et al. Jan 2015 A1
20150012690 Bruce et al. Jan 2015 A1
20150032937 Salessi Jan 2015 A1
20150032938 Salessi Jan 2015 A1
20150067243 Salessi et al. Mar 2015 A1
20150149697 Salessi et al. May 2015 A1
20150149706 Salessi et al. May 2015 A1
20150153962 Salessi et al. Jun 2015 A1
20150169021 Salessi et al. Jun 2015 A1
20150261456 Alcantara et al. Sep 2015 A1
20150261475 Alcantara et al. Sep 2015 A1
20150261797 Alcantara et al. Sep 2015 A1
20150370670 Lu Dec 2015 A1
20150371684 Mataya Dec 2015 A1
20150378932 Souri et al. Dec 2015 A1
20160026402 Alcantara et al. Jan 2016 A1
20160027521 Lu Jan 2016 A1
20160041596 Alcantara et al. Feb 2016 A1
Foreign Referenced Citations (5)
Number Date Country
2005142859 Jun 2005 JP
2005-309847 Nov 2005 JP
200428219 Dec 2004 TW
I420316 Dec 2013 TW
WO 9406210 Mar 1994 WO
Non-Patent Literature Citations (136)
Entry
USPTO Notice of Allowability & attachment(s) dated Jan. 7, 2013 for U.S. Appl. No. 12/876,247.
Office Action dated Sep. 14, 2012 for U.S. Appl. No. 12/876,247.
Office Action dated Feb. 1, 2012 for U.S. Appl. No. 12/876,247.
Notice of Allowance/Allowability dated Mar. 31, 2015 for U.S. Appl. No. 13/475,878.
Office Action dated May 22, 2015 for U.S. Appl. No. 13/253,912.
Office Action for U.S. Appl. No. 12/876,113 dated Mar. 13, 2014.
Advisory Action for U.S. Appl. No. 12/876,113 dated Sep. 6, 2013.
Office Action for U.S. Appl. No. 12/876,113 dated May 14, 2013.
Office Action for U.S. Appl. No. 12/876,113 dated Dec. 21, 2012.
Security Comes to SNMP: The New SNMPv3 Proposed Internet Standard, The Internet Protocol Journal, vol. 1, No. 3, Dec. 1998.
Notice of Allowability for U.S. Appl. No. 12/882,059 dated May 30, 2013.
Notice of Allowability for U.S. Appl. No. 12/882,059 dated Feb. 14, 2013.
Office Action for U.S. Appl. No. 12/882,059 dated May 11, 2012.
Notice of Allowability for U.S. Appl. No. 14/038,684 dated Aug. 1, 2014.
Office Action for U.S. Appl. No. 14/038,684 dated Mar. 17, 2014.
Office Action for U.S. Appl. No. 13/253,912 dated Jul. 16, 2014.
Office Action for U.S. Appl. No. 13/475,878, dated Jun. 23, 2014.
Office Action for U.S. Appl. No. 12/876,113 dated Jul. 11, 2014.
Office Action for U.S. Appl. No. 12/876,113 dated Oct. 16, 2014.
Notice of Allowance for U.S. Appl. No. 12/270,626 dated Oct. 3, 2014.
Office Action for U.S. Appl. No. 12/270,626 dated May 23, 2014.
Office Action for U.S. Appl. No. 12/270,626 dated Apr. 4, 2011.
Office Action for U.S. Appl. No. 12/270,626 dated Dec. 18, 2013.
Office Action for U.S. Appl. No. 12/270,626 dated Mar. 15, 2013.
Office Action for U.S. Appl. No. 12/270,626 dated Aug. 23, 2012.
Notice of Allowance/Allowability for U.S. Appl. No. 13/890,229 dated Feb. 20, 2014.
Office Action for U.S. Appl. No. 13/890,229 dated Oct. 8, 2013.
Office Action for U.S. Appl. No. 12/876,113 dated Dec. 5, 2014.
Notice of Allowance/Allowabilty for U.S. Appl. No. 12/876,113 dated Jun. 22, 2015.
Office Action for U.S. Appl. No. 14/217,249 dated Apr. 23, 2015.
Office Action for U.S. Appl. No. 14/215,414 dated Jun. 4, 2015.
Office Action for U.S. Appl. No. 14/217,467 dated Apr. 27, 2015.
Office Action for U.S. Appl. No. 14/217,436 dated Sep. 11, 2015.
Office Action for U.S. Appl. No. 12/270,626 dated Feb. 3, 2012.
Notice of Allowance/Allowability for U.S. Appl. No. 12/270,626 dated Oct. 3, 2014.
Advisory Action for U.S. Appl. No. 12/876,113 dated Oct. 16, 2014.
Office Action for U.S. Appl. No. 14/297,628 dated Jul. 17, 2015.
Office Action for U.S. Appl. No. 13/475,878 dated Dec. 4, 2014.
Office Action dated Sep. 11, 2015 for U.S. Appl. No. 14/217,436.
Office Action dated Sep. 24, 2015 for U.S. Appl. No. 14/217,334.
Office Action dated Sep. 18, 2015 for Taiwanese Patent Application No. 102144165.
Office Action dated Sep. 29, 2015 for U.S. Appl. No. 14/217,316.
Office Action dated Sep. 28, 2015 for U.S. Appl. No. 14/689,045.
Office Action dated Dec. 5, 2014 for U.S. Appl. No. 14/038,684.
Office Action dated Oct. 8, 2015 for U.S. Appl. No. 14/217,291.
Office Action dated Dec. 15, 2015 for U.S. Appl. No. 13/253,912.
Office Action dated Dec. 17, 2015 for U.S. Appl. No. 14/214,216.
Office Action dated Dec. 17, 2015 for U.S. Appl. No. 14/215,414.
Office Action dated Dec. 17, 2015 for U.S. Appl. No. 14/803,107.
Office Action dated Jan. 15, 2016 for U.S. Appl. No. 14/866,946.
Office Action dated Jan. 11, 2016 for U.S. Appl. No. 14/217,399.
Office Action dated Jan. 15, 2016 for U.S. Appl. No. 14/216,937.
Notice of Allowance and Examiner-Initiated Interview Summary, dated Jan. 29, 2016 for U.S. Appl. No. 14/297,628.
National Science Fountation,Award Abstract #1548968, SBIR Phase I: SSD In-Situ Processing, http://www.nsf.gov/awardsearch/showAward?AWD_ID=1548968 printed on Feb. 13, 2016.
Design-Reuse, NxGn Data Emerges from Stealth Mode to provide a paradigm shift in enterprise storage solution.
http://www.design-reuse.com/news/35111/nxgn-data-intelligent-solutions.html, printed on Feb. 13, 2016.
Office Action for U.S. Appl. No. 14/217,365 dated Feb. 18, 2016.
Office Action for U.S. Appl. No. 14/217,365 dated Mar. 2, 2016.
Office Action for U.S. Appl. No. 14/690,305 dated Feb. 25, 2016.
Office Action for U.S. Appl. No. 14/217,436 dated Feb. 25, 2016.
Office Action for U.S. Appl. No. 14/217,316 dated Feb. 26, 2016.
Office Action for U.S. Appl. No. 14/215,414 dated Mar. 1, 2016.
Final Office Action dated Nov. 19, 2015 for U.S. Appl. No. 14/217,249.
Final Office Action dated Nov. 18, 2015 for U.S. Appl. No. 14/217,467.
Office Action dated Nov. 25, 2015 for U.S. Appl. No. 14/217,041.
Notice of allowance/allowability for U.S. Appl. No. 13/253,912 dated Mar. 21, 2016.
Notice of allowance/allowability for U.S. Appl. No. 14/803,107 dated Mar. 28, 2016.
Office Action for U.S. Appl. No. 14/217,334 dated Apr. 4, 2016.
Notice of allowance/allowability for U.S. Appl. No. 14/217,041 dated Apr. 11, 2016.
Office Action for U.S. Appl. No. 14/616,700 dated Mar. 8, 2016 (applied by Examiner in this present application).
Notice of allowance/allowability for U.S. Appl. No. 14/217,467 dated Apr. 20, 2016.
Office Action for U.S. Appl. No. 14/217,249 dated Apr. 21, 2016.
Notice of allowance/allowability for U.S. Appl. No. 14/214,216 dated.
Office Action for U.S. Appl. No. 14/217,291 dated Jun. 15, 2016.
Office Action for U.S. Appl. No. 14/215,414 dated May 20, 2016.
Office Action for U.S. Appl. No. 14/616,700 dated May 20, 2016 (Applied by Examiner).
Office Action for U.S. Appl. No. 14/689,019 dated May 20, 2016.
Advisory Action for U.S. Appl. No. 14/217,316 dated May 19, 2016.
Advisory Action for U.S. Appl. No. 14/217,334 dated Jun. 13, 2016.
Notice of allowance/allowability for U.S. Appl. No. 14/214,216 dated Apr. 27, 2016.
Notice of allowance/allowability for U.S. Appl. No. 14/217,436 dated May 6, 2016.
Notice of allowance/allowability for U.S. Appl. No. 14/217, 365 dated Oct. 18, 2016.
Office Action for U.S. Appl. No. 14/616,700 dated Oct. 20, 2016 (Issued by Examiner in this patent application).
Office Action for U.S. Appl. No. 14/855,245 dated Oct. 26, 2016.
Office Action for U.S. Appl. No. 14/217, 249 dated Oct. 28, 2016.
Office Action for U.S. Appl. No. 14/217,316 dated Aug. 25, 2016.
Office Action for U.S. Appl. No. 14/690,305 dated Aug. 26, 2016.
Office Action for U.S. Appl. No. 14/217,096 dated Jul. 12, 2016.
Notice of Allowance for U.S. Appl. No. 14/217,399 dated Jul. 20, 2016.
Office Action for U.S. Appl. No. 14/866,946 dated Jul. 29, 2016.
Notice of Allowance for U.S. Appl. No. 14/217,334 dated Jul. 29, 2016.
Office Action for U.S. Appl. No. 14/690,243 dated Aug. 11, 2016.
Office Action for U.S. Appl. No. 14/690,370 dated Aug. 12, 2016.
Working Draft American National Standard Project T10/1601-D Information Technology Serial Attached SCSI—1.1 (SAS—1.1), Mar. 13, 2004 Revision 4.
Advisory Action for U.S. Appl. No. 14/217,291 dated Sep. 9, 2016.
Advisory Action for U.S. Appl. No. 14/217,291 dated Sep. 16, 2016.
Notice of Allowance for U.S. Appl. No. 14/217,291 dated Sep. 12, 2016.
Advisory Action for U.S. Appl. No. 14/217,291 dated Sep. 12, 2016.
Notice of Allowance for U.S. Appl. No. 14/217,291 dated Sep. 23, 2016.
Advisory Action for U.S. Appl. No. 14/217,291 dated Oct. 13, 2016.
Office Action for U.S. Appl. No. 14/217,291 dated Sep. 26, 2016.
Office Action for U.S. Appl. No. 14/217,291 dated Oct. 6, 2016.
Office Action for U.S. Appl. No. 14/616,700 dated Jun. 2, 2017 (issued by Examiner in this application).
Office Action for U.S. Appl. No. 15/268,533 dated Jun. 2, 2017.
Office Action for U.S. Appl. No. 15/268,536 dated Apr. 27, 2017.
Office Action for U.S. Appl. No. 15/368,598 dated May 19, 2017.
Office Action for U.S. Appl. No. 14/217,399 dated Nov. 1, 2016.
Office Action for U.S. Appl. No. 14/217,291 dated Nov. 3, 2016.
Office Action for U.S. Appl. No. 14/217,947 dated Nov. 4, 2016.
Office Action for U.S. Appl. No. 14/216,627 dated Nov. 7, 2016.
Office Action for U.S. Appl. No. 14/689,019 dated Nov. 18, 2016.
Office Action for U.S. Appl. No. 14/684,399 dated Nov. 21, 2016.
Notice of Allowance for U.S. Appl. No. 14/689,045 dated Nov. 21, 2016.
Notice of Allowance for U.S. Appl. No. 14/217,334 dated Nov. 23, 2016.
Advisory Action for U.S. Appl. No. 14/690,305 dated Nov. 25, 2016.
Office Action for U.S. Appl. No. 14/216,937 dated Aug. 15, 2016.
Notice of Allowance for U.S. Appl. No. 14/217,096 dated Dec. 5, 2016.
Notice of Allowance for U.S. Appl. No. 14/217,161 dated Dec. 30, 2016.
Office Action for U.S. Appl. No. 14/866,946 dated Jan. 5, 2017.
Office Action for U.S. Appl. No. 14/688,209 dated Jan. 11, 2017.
Amazon Route 53 Developer Guide API Version Apr. 1, 2013, copyright 2017 by Amazon Web Services.
Host Bus Adapters (HBAs): What you need to know about networking workhorse by Alan Earls, Feb. 2003.
Office Action for U.S. Appl. No. 14/690,243 dated Jan. 13, 2017.
Office Action for U.S. Appl. No. 14/232,801 dated Jan. 19, 2017.
Office Action for U.S. Appl. No. 14/866,946 dated Jul. 27, 2017.
Robert Cooksey et al., A Stateless, Content-Directed Data Prefetching Mechanism, 2002.
Notice of Allowance for U.S. Appl. No. 14/215,414 dated Jan. 20, 2017.
Advisory Action for U.S. Appl. No. 14/217,249 dated Jan. 26, 2017.
Notice of Allowance for U.S. Appl. No. 14/687,700 dated Jan. 27, 2016.
Office Action for U.S. Appl. No. 14/690,339 dated Feb. 3, 2017.
Office Action for U.S. Appl. No. 14/616,700 dated Feb. 9, 2017.
Notice of Allowance for U.S. Appl. No. 14/217,365 dated Feb. 10, 2017.
Office Action for U.S. Appl. No. 14/690,305 dated Feb. 10, 2017.
Office Action for U.S. Appl. No. 14/690,349 dated Feb. 8, 2017.
Advisory Action for U.S. Appl. No. 14/689,019 dated Feb. 17, 2017.
Office Action for U.S. Appl. No. 14/690,349 dated Feb. 27, 2017.
Provisional Applications (1)
Number Date Country
60988728 Nov 2007 US
Continuations (1)
Number Date Country
Parent 12270626 Nov 2008 US
Child 14616700 US