A storage device is disclosed. The storage device may include storage to store data and a controller to manage reading data from and writing data to the storage. The controller may also include a receiver to receive a plurality of requests, information determination logic to determine information about the plurality of requests, storage for the information about a plurality of requests, and sharing logic to share the information with a management controller.
|
1. A storage device, comprising:
a first storage to store data;
a storage device controller to manage reading data from or writing data to the first storage responsive to a first request and a second request, the storage device controller including:
a second storage for a first information about the first request and a second information about the second request; and
a receiver to receive the first request and the second request,
wherein the storage device controller is configured to determine the first information about the first request and the second information about the second request, and to share the first information about the first request and the second information about the second request with a management controller.
10. A method, comprising:
receiving a first request at a storage device from a host;
receiving a second request at the storage device from the host;
executing the first request on the storage device;
executing the second request on the storage device;
returning a first result of the first request from the storage device to the host;
returning a second result of the second request from the storage device to the host;
determining a first information about the first request, wherein the first information describes a first performance of the storage device in executing the first request on the storage device;
determining a second information about the second request, wherein the second information describes a second performance of the storage device in executing the second request on the storage device; and
sharing the first information and the second information with a management controller by the storage device over a connection.
19. An article, comprising a non-transitory storage medium, the non-transitory storage medium having stored thereon instructions that, when executed by a machine, result in:
receiving a first request at a storage device from a host;
receiving a second request at the storage device from the host;
executing the first request on the storage device;
executing the second request on the storage device;
returning a first result of the first request from the storage device to the host;
returning a second result of the second request from the storage device to the host;
determining a first information about the first request, wherein the first information describes a first performance of the storage device in executing the first request on the storage device;
determining a second information about the second request, wherein the second information describes a second performance of the storage device in executing the second request on the storage device; and
sharing the first information and the second information with a management controller by the storage device over a connection.
2. A storage device according to
3. A storage device according to
wherein the management controller is configured to use the first information about the first request to determine a tail latency of the storage device and to assign an application to the storage device based in part on a requested level of service of the application and the tail latency of the storage device.
4. A storage device according to
5. A storage device according to
wherein the storage device controller is configured to write the first information to the buffer and the management controller is configured to read the first information from the buffer.
6. A storage device according to
the receiver is configured to receive a request for data from the management controller; and
the storage device controller includes:
a data selector to select the data from the first information about the first request; and
a transmitter to transmit the selected data to the management controller.
7. A storage device according to
8. A storage device according to
9. A storage device according to
11. A method according to
12. A method according to
determining the first information about the first request includes determining the first information about the first request based at least in part on execution of the first request by the storage device,
wherein the management controller is configured to use the first information about the first request to determine a tail latency of the storage device and to assign an application to the storage device based in part on a requested level of service of the application and the tail latency of the storage device.
13. A method according to
Wherein the management controller is configured to read the first information from the buffer.
14. A method according to
receiving a request from the management controller to access the buffer; and
authenticating the management controller.
15. A method according to
receiving a request for data from the management controller;
selecting data from the first information about the first request; and
sending the data selected from the first information about the first request to the management controller.
16. A method according to
17. A method according to
18. A method according to
20. An article according to
21. A storage device according to
the first storage includes a first type;
the second storage includes a second type; and
the second type is different from the first type.
|
This application is a continuation of U.S. patent application Ser. No. 16/697,177, filed Nov. 26, 2019, now allowed, which is a continuation of U.S. patent application Ser. No. 15/653,479, filed Jul. 18, 2017, now U.S. Pat. No. 10,545,664, issued Jan. 28, 2020, which claims the benefit of U.S. Provisional Patent Application Ser. No. 62/484,387, filed Apr. 11, 2017, all of which are incorporated by reference herein for all purposes.
The inventive concepts relate generally to Solid State Drives (SSDs), and more particularly to managing SSDs of differing performance capabilities.
For hyperscalers, the non-deterministic behaviors of Solid State Drives (SSDs), and especially tail latency, are a major issue. Tail latency—the worst case or near-worst case performance of a storage device—may have a detrimental impact on the overall performance of a hyperscaled application, even though tail latency may affect only a small percentage of requests.
To counter problems such as tail latency, hyperscalers may and do request specific functionality in the storage devices they use. But different storage device vendors may implement the functionalities in different ways. As a result, the performance of those functionalities in the storage devices may vary across vendors, and even across storage devices offered by a particular vendor.
It might be possible for a single vendor to classify the storage devices it offers based on the performance of these functionalities. For example, a single vendor might be able to classify its storage devices based on tail latency identifying particular storage device offerings as offering top-tier, middle-tier, and lowest-tier performance. It might even be possible for vendors to agree on a standard for classifying storage devices, so that a “top-tier” storage device from one vendor might be considered comparable to a “top-tier” storage device from another storage vendor.
But there are problems with this approach. First, different storage devices may offer different functionality. If one storage device model from one vendor implements two different requested functionalities and another storage device model from another vendor implements only one requested functionality, should those two storage device models be considered comparable? Second, manufacturing variabilities might result in varying performance levels even within a particular storage device model from a single vendor, meaning that two different devices of the same model might be more appropriately classified differently, a fact that might not be determined without rigorous testing of the storage devices. Third, using a “one size fits all” classification system might not meet the needs of individual hyperscalers. With enterprises leasing computing resources more and purchasing their own servers less, vendors are more likely to need to vary their workloads for different subscribers.
A need remains for a way to determine the performance characteristics of storage devices for classification by data centers.
Reference will now be made in detail to embodiments of the inventive concept, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth to enable a thorough understanding of the inventive concept. It should be understood, however, that persons having ordinary skill in the art may practice the inventive concept without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first module could be termed a second module, and, similarly, a second module could be termed a first module, without departing from the scope of the inventive concept.
The terminology used in the description of the inventive concept herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the inventive concept. As used in the description of the inventive concept and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. The components and features of the drawings are not necessarily drawn to scale.
To address the problems of the prior art, a management controller, such as a Baseboard Management Controller (BMC) may manage and keep track of all Solid State Drives (SSDs) residing in the chassis. Each SSD device may track all completed transactions in terms of the actual time required to complete a transaction. Collectively, device latency counter(s) inside each SSD controller may keep track of all transactions for each application/host. Each SSD may periodically report back to the BMC.
Hyperscalers/users may use the information from the BMC to determine how to allocate storage resources (i.e., SSDs) by matching storage resources to the applications' latency requirements and leasing/subscription rates. Embodiments of the inventive concept would enable customers who are willing to pay a higher fee in order to have the lowest tail latency storage, and enable service providers such as AWS, Google, and Azure to offer better solutions for higher fees.
Embodiments of the inventive concept may use a BMC to collect latency information from all SSDs residing in the same chassis. Before allocating computing and storage resources, a cloud-based service provider may retrieve the needed information from the BMC. Thereafter, the service provider may easily identify and match computing and storage resources for certain premium users. For example, the BMC may identify its own SSDs with lowest latency for “Platinum,” mid-range latency for “Gold”, and highest latency for “Bronze” rates respectively.
An SSD may perform the following functions:
Computer machine 105, regardless of its specific form, may include processor 110, memory 115, and Solid State Drive (SSD) 120. Processor 110 may be any variety of processor: for example, an Intel Xeon, Celeron, Itanium, or Atom processor, an AMD Opteron processor, an ARM processor, etc. While
Storage device 120 may be any variety of storage device: for example, a hard disk drive or a Solid State Drive (SSD). Embodiments of the inventive concept may include any variety of storage device capable of providing the information used to manage storage devices. Thus, while this document and the drawings might focus at times on SSDs as storage devices, the use of SSDs is merely exemplary, and the concepts described herein may be extended to any storage device capable of providing the information used to manage the storage devices. Storage device 120 may be controlled by device driver 130, which may reside within memory 115. While
Baseboard Management Controller (BMC) 135 is used in servers, PCs, switches and other computer-based products. Generally speaking, BMC 135 communicates with sensors, measuring internal physical variables such as temperature, humidity, power-supply voltage, fan speeds, communications parameters, and operating system (OS) functions. If any of these variables happens to stray outside specified limits, the administrator may be notified. That person may then take corrective action by remote control. In some cases, BMC 135 may take some corrective actions such as increasing fan speeds or rebooting the failed subsystems. The monitored device/system may be power cycled or rebooted remotely, as necessary and/or appropriate. In this way, a single administrator may remotely manage numerous servers and other devices simultaneously, saving on the overall operating cost of the network and helping to ensure its availability.
Because BMC 135 is connected to various components of computer machine 105, which may include storage device 120, BMC 135 may be used to control these components. This control may include accessing the characteristics of storage device 120. These characteristics may then be used to determine which storage device is the “best fit” for storing data relating to a particular application running on computer machine 105 (or another connected machine). While
In embodiments of the inventive concept, storage devices 120-1 through 120-n may collect information about their operation. This information may be reported to BMC 135 via the control plane over PCIe switch 310. In this manner, communications with BMC 135 do not interfere with communications over the data plane via Ethernet switch 305. Embodiments of the inventive concept may use other desired communication paths for the control plane. For example, the control plane between BMC 135 and storage devices 120-1 through 120-n may use the System Management Bus (SMBus), rather than PCIe switch 310. Any reference to PCIe switch 310 should be understood to include alternative control planes like SMBus.
In
SSD controller 410 may also include embedded microprocessor 430. Embedded microprocessor 430 may be any desired processor included within SSD 120. Embedded microprocessor 430 may run applications on behalf of computer machine 105 of
SSD controller 410 may also include timestamper 525. Timestamper 525 may apply a timestamp to the information stored in storage 505. The timestamp may then be used to filter what information is provided to BMC 135 of
SSD controller 410 may also include application identifier 530. Application identifier 530 may identify an application from which a particular request was received. For example, if embedded microprocessor 430 of
Set 605 represents some possible data that may be tracked by storage device 120 of
While storage device 120 of
Generally, the shape of histogram 705 is expected to be approximately a bell curve (or Gaussian distribution), although other distributions are possible and might be expected. The exact shape may vary, as may the mean and standard deviation of histogram 705.
Histogram 705 shows some of the information that may be sent from storage device 120 of
In
While
The exact implementation of information determination logic 515 will vary depending on the form information 810-1 through 810-4 takes. For example, if information 810-1 through 810-4 measures read latency 610 of
Sharing logic 520 may include Controller Memory Buffer (CMB) 905, authenticator 910, data selector 915, log page generator 920, and transmitter 925. CMB 905 may be a storage within storage device 120 of
To prevent unauthorized access to CMB 905, sharing logic 520 may include authenticator 910. Authenticator 910 may determine whether any particular component, such as BMC 135 of
While sharing logic 520 may share all information about storage device 120 of
Data selector 915 may also include histogram generator 930. Histogram generator 930 may generate histogram 705 of
When storage device 120 of
Data selector 915 may also be used when storage device 120 of
At block 1030, information determination logic 515 may determine information about storage device 120 of
In
The following discussion is intended to provide a brief, general description of a suitable machine or machines in which certain aspects of the inventive concept may be implemented. The machine or machines may be controlled, at least in part, by input from conventional input devices, such as keyboards, mice, etc., as well as by directives received from another machine, interaction with a virtual reality (VR) environment, biometric feedback, or other input signal. As used herein, the term “machine” is intended to broadly encompass a single machine, a virtual machine, or a system of communicatively coupled machines, virtual machines, or devices operating together. Exemplary machines include computing devices such as personal computers, workstations, servers, portable computers, handheld devices, telephones, tablets, etc., as well as transportation devices, such as private or public transportation, e.g., automobiles, trains, cabs, etc.
The machine or machines may include embedded controllers, such as programmable or non-programmable logic devices or arrays, Application Specific Integrated Circuits (ASICs), embedded computers, smart cards, and the like. The machine or machines may utilize one or more connections to one or more remote machines, such as through a network interface, modem, or other communicative coupling. Machines may be interconnected by way of a physical and/or logical network, such as an intranet, the Internet, local area networks, wide area networks, etc. One skilled in the art will appreciate that network communication may utilize various wired and/or wireless short range or long range carriers and protocols, including radio frequency (RF), satellite, microwave, Institute of Electrical and Electronics Engineers (IEEE) 802.11, Bluetooth®, optical, infrared, cable, laser, etc.
Embodiments of the present inventive concept may be described by reference to or in conjunction with associated data including functions, procedures, data structures, application programs, etc. which when accessed by a machine results in the machine performing tasks or defining abstract data types or low-level hardware contexts. Associated data may be stored in, for example, the volatile and/or non-volatile memory, e.g., RAM, ROM, etc., or in other storage devices and their associated storage media, including hard-drives, floppy-disks, optical storage, tapes, storage, memory sticks, digital video disks, biological storage, etc. Associated data may be delivered over transmission environments, including the physical and/or logical network, in the form of packets, serial data, parallel data, propagated signals, etc., and may be used in a compressed or encrypted format. Associated data may be used in a distributed environment, and stored locally and/or remotely for machine access.
Embodiments of the inventive concept may include a tangible, non-transitory machine-readable medium comprising instructions executable by one or more processors, the instructions comprising instructions to perform the elements of the inventive concepts as described herein.
Having described and illustrated the principles of the inventive concept with reference to illustrated embodiments, it will be recognized that the illustrated embodiments may be modified in arrangement and detail without departing from such principles, and may be combined in any desired manner. And, although the foregoing discussion has focused on particular embodiments, other configurations are contemplated. In particular, even though expressions such as “according to an embodiment of the inventive concept” or the like are used herein, these phrases are meant to generally reference embodiment possibilities, and are not intended to limit the inventive concept to particular embodiment configurations. As used herein, these terms may reference the same or different embodiments that are combinable into other embodiments.
The foregoing illustrative embodiments are not to be construed as limiting the inventive concept thereof. Although a few embodiments have been described, those skilled in the art will readily appreciate that many modifications are possible to those embodiments without materially departing from the novel teachings and advantages of the present disclosure. Accordingly, all such modifications are intended to be included within the scope of this inventive concept as defined in the claims.
Embodiments of the inventive concept may extend to the following statements, without limitation:
Statement 1. An embodiment of the inventive concept includes a storage device, comprising:
storage to store data;
a storage device controller to manage reading data from and writing data to the storage responsive to a plurality of requests, the storage device controller including:
Statement 2. An embodiment of the inventive concept includes a storage device according to statement 1, wherein the management controller includes a Baseboard Management Controller (BMC).
Statement 3. An embodiment of the inventive concept includes a storage device according to statement 1, wherein the storage device includes a Solid State Drive (SSD).
Statement 4. An embodiment of the inventive concept includes a storage device according to statement 3, wherein the SSD supports a Non-Volatile Memory Express Over Fabrics (NVMeoF) protocol.
Statement 5. An embodiment of the inventive concept includes a storage device according to statement 3, wherein the SSD communicates with the management controller over at least one Peripheral Component Interconnect Express (PCIe) lane.
Statement 6. An embodiment of the inventive concept includes a storage device according to statement 5, wherein the SSD receives the plurality of requests over an Ethernet port.
Statement 7. An embodiment of the inventive concept includes a storage device according to statement 1, wherein the information determination logic is operative to determine the information about each of plurality of requests while each of the plurality of requests is executed by the storage device.
Statement 8. An embodiment of the inventive concept includes a storage device according to statement 1, wherein the information are drawn from a set including read latencies, write latencies, program fail counts, erase fail counts, wear level counts, bit error rates, and interface bit error rates.
Statement 9. An embodiment of the inventive concept includes a storage device according to statement 1, wherein:
the information determination logic is operative to determine statistics for the plurality of requests; and
the sharing logic is operative to share the statistics for the plurality of requests with the management controller.
Statement 10. An embodiment of the inventive concept includes a storage device according to statement 1, wherein the sharing logic includes a Controller Memory Buffer (CMB) that may store the information about each of the plurality of requests.
Statement 11. An embodiment of the inventive concept includes a storage device according to statement 10, wherein the sharing logic includes an authenticator to authenticate the management controller before permitting the management controller to access the CMB.
Statement 12. An embodiment of the inventive concept includes a storage device according to statement 1, wherein:
the receiver is operative to receive a request for data from the management controller; and
the sharing logic includes:
Statement 13. An embodiment of the inventive concept includes a storage device according to statement 12, wherein:
the sharing logic further includes a Log Page generator to generate a Log Page from the selected data; and
the transmitter is operative to transmit the Log Page to the management controller.
Statement 14. An embodiment of the inventive concept includes a storage device according to statement 12, wherein the selected data is a subset of the information about each of the plurality of requests.
Statement 15. An embodiment of the inventive concept includes a storage device according to statement 12, wherein the data selector includes a histogram generator to generate a histogram from the selected data.
Statement 16. An embodiment of the inventive concept includes a storage device according to statement 1, wherein the storage device controller further includes a timestamper to timestamp the information for each of the plurality of requests.
Statement 17. An embodiment of the inventive concept includes a storage device according to statement 1, wherein the storage device controller further includes an application identifier to determine an application ID for each of the plurality of requests.
Statement 18. An embodiment of the inventive concept includes a storage device according to statement 17, wherein the storage device includes an embedded microprocessor running an application identified by the application ID.
Statement 19. An embodiment of the inventive concept includes a method, comprising:
receiving a plurality of requests at a storage device;
executing each of the plurality of requests on the storage device;
returning results of each of the plurality of requests from the storage device;
determining information for each of the plurality of requests, wherein the information describes a performance of the storage device in executing each of the plurality of requests on the storage device; and
sharing the information with a management controller.
Statement 20. An embodiment of the inventive concept includes a method according to statement 19, wherein the management controller includes a Baseboard Management Controller (BMC).
Statement 21. An embodiment of the inventive concept includes a method according to statement 19, wherein the storage device includes a Solid State Drive (SSD).
Statement 22. An embodiment of the inventive concept includes a method according to statement 21, wherein the SSD supports a Non-Volatile Memory Express Over Fabrics (NVMeoF) protocol.
Statement 23. An embodiment of the inventive concept includes a method according to statement 21, wherein sharing the information with a management controller includes sharing the information with the management controller over at least one Peripheral Component Interconnect Express (PCIe) lane.
Statement 24. An embodiment of the inventive concept includes a method according to statement 23, wherein receiving a plurality of requests at a storage device includes receiving the plurality of requests at the SSD over an Ethernet port.
Statement 25. An embodiment of the inventive concept includes a method according to statement 19, wherein determining information for each of the plurality of requests includes determining the information for each of the plurality of requests while executing each of the plurality of the requests.
Statement 26. An embodiment of the inventive concept includes a method according to statement 19, wherein the information are drawn from a set including read latencies, write latencies, program fail counts, erase fail counts, wear level counts, bit error rates, and interface bit error rates.
Statement 27. An embodiment of the inventive concept includes a method according to statement 19, wherein:
determining information for each of the plurality of requests includes determining statistics for the plurality of requests; and
sharing the information with a management controller includes sharing the statistics for the plurality of requests with the management controller.
Statement 28. An embodiment of the inventive concept includes a method according to statement 19, wherein sharing the information with a management controller includes storing the information for each of the plurality of requests in a Controller Memory Buffer (CMB).
Statement 29. An embodiment of the inventive concept includes a method according to statement 28, wherein sharing the information with a management controller further includes:
receiving a request from the management controller to access the CMB; and
authenticating the management controller.
Statement 30. An embodiment of the inventive concept includes a method according to statement 19, wherein sharing the information with a management controller includes:
receiving a request for data from the management controller;
selecting data from the information for each of the plurality of requests; and
sending the data from the information for each of the plurality of requests to the management controller.
Statement 31. An embodiment of the inventive concept includes a method according to statement 30, wherein:
sharing the information with a management controller further includes generate a Log page including the data; and
sending the data from the information for each of the plurality of requests to the management controller includes sending the Log Page to the management controller.
Statement 32. An embodiment of the inventive concept includes a method according to statement 30, wherein the data is a subset of the information for each of the plurality of requests.
Statement 33. An embodiment of the inventive concept includes a method according to statement 30, wherein selecting data from the information for each of the plurality of requests includes generating a histogram from the information for each of the plurality of requests as the data.
Statement 34. An embodiment of the inventive concept includes a method according to statement 19, wherein determining information for each of the plurality of requests includes timestamping the information for each of the plurality of requests.
Statement 35. An embodiment of the inventive concept includes a method according to statement 34, wherein sharing the information with a management controller includes selecting the information with a timestamp more recent than an earlier timestamp.
Statement 36. An embodiment of the inventive concept includes a method according to statement 19, wherein determining information for each of the plurality of requests includes determining an application ID for each of the plurality of requests.
Statement 37. An embodiment of the inventive concept includes a method according to statement 36, wherein the application ID identifies an application running on a microprocessor embedded in the storage device.
Statement 38. An embodiment of the inventive concept includes an article, comprising a non-transitory storage medium, the non-transitory storage medium having stored thereon instructions that, when executed by a machine, result in:
receiving a plurality of requests at a storage device;
executing each of the plurality of requests on the storage device;
returning results of each of the plurality of requests from the storage device;
determining information for each of the plurality of requests, wherein the information describes a performance of the storage device in executing each of the plurality of requests on the storage device; and
sharing the information with a management controller.
Statement 39. An embodiment of the inventive concept includes an article according to statement 38, wherein the management controller includes a Baseboard Management Controller (BMC).
Statement 40. An embodiment of the inventive concept includes an article according to statement 38, wherein the storage device includes a Solid State Drive (SSD).
Statement 41. An embodiment of the inventive concept includes an article according to statement 40, wherein the SSD supports a Non-Volatile Memory Express Over Fabrics (NVMeoF) protocol.
Statement 42. An embodiment of the inventive concept includes an article according to statement 40, wherein sharing the information with a management controller includes sharing the information with the management controller over at least one Peripheral Component Interconnect Express (PCIe) lane.
Statement 43. An embodiment of the inventive concept includes an article according to statement 42, wherein receiving a plurality of requests at a storage device includes receiving the plurality of requests at the SSD over an Ethernet port.
Statement 44. An embodiment of the inventive concept includes an article according to statement 38, wherein determining information for each of the plurality of requests includes determining the information for each of the plurality of requests while executing each of the plurality of the requests.
Statement 45. An embodiment of the inventive concept includes an article according to statement 38, wherein the information are drawn from a set including read latencies, write latencies, program fail counts, erase fail counts, wear level counts, bit error rates, and interface bit error rates.
Statement 46. An embodiment of the inventive concept includes an article according to statement 38, wherein:
determining information for each of the plurality of requests includes determining statistics for the plurality of requests; and
sharing the information with a management controller includes sharing the statistics for the plurality of requests with the management controller.
Statement 47. An embodiment of the inventive concept includes an article according to statement 38, wherein sharing the information with a management controller includes storing the information for each of the plurality of requests in a Controller Memory Buffer (CMB).
Statement 48. An embodiment of the inventive concept includes an article according to statement 47, wherein sharing the information with a management controller further includes:
receiving a request from the management controller to access the CMB; and
authenticating the management controller.
Statement 49. An embodiment of the inventive concept includes an article according to statement 38, wherein sharing the information with a management controller includes:
receiving a request for data from the management controller;
selecting data from the information for each of the plurality of requests; and
sending the data from the information for each of the plurality of requests to the management controller.
Statement 50. An embodiment of the inventive concept includes an article according to statement 49, wherein:
sharing the information with a management controller further includes generate a Log page including the data; and
sending the data from the information for each of the plurality of requests to the management controller includes sending the Log Page to the management controller.
Statement 51. An embodiment of the inventive concept includes an article according to statement 49, wherein the data is a subset of the information for each of the plurality of requests.
Statement 52. An embodiment of the inventive concept includes an article according to statement 49, wherein selecting data from the information for each of the plurality of requests includes generating a histogram from the information for each of the plurality of requests as the data.
Statement 53. An embodiment of the inventive concept includes an article according to statement 38, wherein determining information for each of the plurality of requests includes timestamping the information for each of the plurality of requests.
Statement 54. An embodiment of the inventive concept includes an article according to statement 53, wherein sharing the information with a management controller includes selecting the information with a timestamp more recent than an earlier timestamp.
Statement 55. An embodiment of the inventive concept includes an article according to statement 38, wherein determining information for each of the plurality of requests includes determining an application ID for each of the plurality of requests.
Statement 56. An embodiment of the inventive concept includes an article according to statement 55, wherein the application ID identifies an application running on a microprocessor embedded in the storage device.
Consequently, in view of the wide variety of permutations to the embodiments described herein, this detailed description and accompanying material is intended to be illustrative only, and should not be taken as limiting the scope of the inventive concept. What is claimed as the inventive concept, therefore, is all such modifications as may come within the scope and spirit of the following claims and equivalents thereto.
Olarig, Sompong Paul, Kachare, Ramdas P., Wu, Wentao
Patent | Priority | Assignee | Title |
Patent | Priority | Assignee | Title |
7191283, | Aug 21 2003 | Western Digital Technologies, INC | Grouping of storage media based on parameters associated with the storage media |
9043184, | Oct 12 2011 | NetApp, Inc. | System and method for identifying underutilized storage capacity |
9417803, | Sep 20 2011 | Apple Inc. | Adaptive mapping of logical addresses to memory devices in solid state drives |
9418088, | Dec 02 2015 | International Business Machines Corporation | Identification of storage system elements causing performance degradation |
9423967, | Sep 15 2010 | Pure Storage, Inc. | Scheduling of I/O writes in a storage environment |
9471517, | Apr 14 2015 | SK Hynix Inc. | Memory system, memory module and method to backup and restore system using command address latency |
9541987, | Jun 28 2013 | Intel Corporation | Generic host-based controller latency method and appartus |
9563502, | Feb 11 2016 | Seagate Technology LLC | Read retry operations with read reference voltages ranked for different page populations of a memory |
9582058, | Nov 29 2013 | Western Digital Technologies, INC | Power inrush management of storage devices |
20070011330, | |||
20120072798, | |||
20130179631, | |||
20130239111, | |||
20140215177, | |||
20140324862, | |||
20150169221, | |||
20150254088, | |||
20150331473, | |||
20170004193, | |||
20170031857, | |||
20170102874, | |||
20170132169, | |||
20180083854, | |||
20180095904, | |||
20180165016, | |||
20180253500, | |||
20180260135, | |||
20180284011, | |||
20180288090, | |||
20180293147, | |||
20180293171, | |||
KR20160138448, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Jul 16 2017 | KACHARE, RAMDAS P | SAMSUNG ELECTRONICS CO , LTD | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 064339 | /0871 | |
Jul 16 2017 | OLARIG, SOMPONG PAUL | SAMSUNG ELECTRONICS CO , LTD | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 064339 | /0871 | |
Jul 16 2017 | WU, WENTAO | SAMSUNG ELECTRONICS CO , LTD | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 064339 | /0871 | |
Jun 23 2021 | Samsung Electronics Co., Ltd. | (assignment on the face of the patent) | / |
Date | Maintenance Fee Events |
Jun 23 2021 | BIG: Entity status set to Undiscounted (note the period is included in the code). |
Date | Maintenance Schedule |
Aug 01 2026 | 4 years fee payment window open |
Feb 01 2027 | 6 months grace period start (w surcharge) |
Aug 01 2027 | patent expiry (for year 4) |
Aug 01 2029 | 2 years to revive unintentionally abandoned end. (for year 4) |
Aug 01 2030 | 8 years fee payment window open |
Feb 01 2031 | 6 months grace period start (w surcharge) |
Aug 01 2031 | patent expiry (for year 8) |
Aug 01 2033 | 2 years to revive unintentionally abandoned end. (for year 8) |
Aug 01 2034 | 12 years fee payment window open |
Feb 01 2035 | 6 months grace period start (w surcharge) |
Aug 01 2035 | patent expiry (for year 12) |
Aug 01 2037 | 2 years to revive unintentionally abandoned end. (for year 12) |