US20210255801A1 - Information handling system having improved host memory buffer for input/output requests - Google Patents
Information handling system having improved host memory buffer for input/output requests Download PDFInfo
- Publication number
- US20210255801A1 US20210255801A1 US16/794,404 US202016794404A US2021255801A1 US 20210255801 A1 US20210255801 A1 US 20210255801A1 US 202016794404 A US202016794404 A US 202016794404A US 2021255801 A1 US2021255801 A1 US 2021255801A1
- Authority
- US
- United States
- Prior art keywords
- solid
- state drive
- host
- write
- write request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/061—Improving I/O performance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
- G06F12/023—Free address space management
- G06F12/0238—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory
- G06F12/0246—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory in block erasable memory, e.g. flash memory
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
- G06F12/0802—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
- G06F12/0866—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches for peripheral storage systems, e.g. disk cache
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/061—Improving I/O performance
- G06F3/0611—Improving I/O performance in relation to response time
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
- G06F3/0656—Data buffering arrangements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
- G06F3/0659—Command handling arrangements, e.g. command buffers, queues, command scheduling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/0671—In-line storage system
- G06F3/0673—Single storage device
- G06F3/0679—Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/0671—In-line storage system
- G06F3/0673—Single storage device
- G06F3/068—Hybrid storage device
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
- G06F2212/10—Providing a specific technical effect
- G06F2212/1016—Performance improvement
- G06F2212/1024—Latency reduction
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
- G06F2212/72—Details relating to flash memory management
- G06F2212/7201—Logical to physical mapping or translation of blocks or pages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
- G06F2212/72—Details relating to flash memory management
- G06F2212/7203—Temporary buffering, e.g. using volatile buffer or dedicated buffer blocks
Abstract
Description
- This disclosure generally relates to information handling systems, and more particularly relates to redirecting write operations to host memory buffers and/or to prioritizing read operations in read/write mixed input/output requests.
- As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option is an information handling system. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes. Because technology and information handling needs and requirements may vary between different applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software resources that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.
- A host memory buffer is configured as a write cache for prioritizing read operations. When a peripheral device (such as a solid-state drive) receives a mixture of read requests and write requests, the write requests may be suspended or deferred to first execute the read requests. The write requests may thus be cached to the host memory buffer, thus allowing the peripheral device to process the read requests for relatively immediate response. Once the read requests are completed, the peripheral device may begin executing a queue of the write requests stored to the host memory buffer. This caching strategy results in a thirty percent (30%) improvement in drive performance.
- It will be appreciated that for simplicity and clarity of illustration, elements illustrated in the Figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements are exaggerated relative to other elements. Embodiments incorporating teachings of the present disclosure are shown and described with respect to the drawings presented herein, in which:
-
FIG. 1 is a block diagram of a generalized information handling system; -
FIGS. 2-3 illustrate a host memory buffer, according to exemplary embodiments; -
FIGS. 4-7 illustrate a caching method, according to exemplary embodiments; -
FIGS. 8-9 illustrate performance improvements, according to exemplary embodiments; and -
FIG. 10 illustrates a method or algorithm for caching to the host memory buffer, according to exemplary embodiments. - The use of the same reference symbols in different drawings indicates similar or identical items.
- The following description in combination with the Figures is provided to assist in understanding the teachings disclosed herein. The following discussion will focus on specific implementations and embodiments of the teachings. This focus is provided to assist in describing the teachings, and should not be interpreted as a limitation on the scope or applicability of the teachings.
-
FIG. 1 illustrates an embodiment of aninformation handling system 100 includingprocessors chipset 110,memory 120,graphics adapter 130 connected tovideo display 134, non-volatile RAM (NV-RAM) 140 that includes a basic input and output system/extensible firmware interface (BIOS/EFI) module 142,disk controller 150, hard disk drive (HDD) 154, optical disk drive (ODD) 156,disk emulator 160 connected to solid state drive (SSD) 164, an input/output (I/O)interface 170 connected to an add-onresource 174, a trusted platform module (TPM) 176, anetwork interface device 180, and a baseboard management controller (BMC) 190.Processor 102 is connected tochipset 110 viaprocessor interface 106, andprocessor 104 is connected tochipset 110 viaprocessor interface 108. -
Chipset 110 represents an integrated circuit or group of integrated circuits that manages data flow betweenprocessors information handling system 100. In a particular embodiment,chipset 110 represents a pair of integrated circuits, such as a north bridge component and a south bridge component. In another embodiment, some or all of the functions and features ofchipset 110 are integrated with one or more ofprocessors Memory 120 is connected tochipset 110 via amemory interface 122. An example ofmemory interface 122 includes a Double Data Rate (DDR) memory channel, andmemory 120 represents one or more DDR Dual In-Line Memory Modules (DIMMs). In a particular embodiment,memory interface 122 represents two or more DDR channels. In another embodiment, one or more ofprocessors memory interface 122 that provides a dedicated memory for the processors. A DDR channel and the connected DDR DIMMs can be in accordance with a particular DDR standard, such as a DDR3 standard, a DDR4 standard, a DDR5 standard, or the like.Memory 120 may further represent various combinations of memory types, such as Dynamic Random Access Memory (DRAM) DIMMs, Static Random Access Memory (SRAM) DIMMs, non-volatile DIMMs (NV-DIMMs), storage class memory devices, Read-Only Memory (ROM) devices, or the like. -
Graphics adapter 130 is connected tochipset 110 via agraphics interface 132, and provides avideo display output 136 to avideo display 134. An example of agraphics interface 132 includes a peripheral component interconnect-express interface (PCIe) andgraphics adapter 130 can include a four lane (×4) PCIe adapter, an eight lane (×8) PCIe adapter, a 16-lane (×16) PCIe adapter, or another configuration, as needed or desired. In a particular embodiment,graphics adapter 130 is provided on a system printed circuit board (PCB).Video display output 136 can include a digital video interface (DVI), a high definition multimedia interface (HDMI), DisplayPort interface, or the like.Video display 134 can include a monitor, a smart television, an embedded display such as a laptop computer display, or the like. - NV-
RAM 140,disk controller 150, and I/O interface 170 are connected tochipset 110 via I/O channel 112. An example of I/O channel 112 includes one or more point-to-point PCIe links betweenchipset 110 and each of NV-RAM 140,disk controller 150, and I/O interface 170.Chipset 110 can also include one or more other I/O interfaces, including an Industry Standard Architecture (ISA) interface, a Small Computer Serial Interface (SCSI) interface, an Inter-Integrated Circuit (I2C) interface, a System Packet Interface (SPI), a Universal Serial Bus (USB), another interface, or a combination thereof. NV-RAM 140 includes BIOS/EFI module 142 that stores machine-executable code (BIOS/EFI code) that operates to detect the resources ofinformation handling system 100, to provide drivers for the resources, to initialize the resources, and to provide common access mechanisms for the resources. The functions and features of BIOS/EFI module 142 will be further described below. -
Disk controller 150 includes adisk interface 152 that connects thedisc controller 150 to HDD 154, to ODD 156, and todisk emulator 160.Disk interface 152 may include an integrated drive electronics (IDE) interface, an advanced technology attachment (ATA) such as a parallel ATA (PATA) interface or a serial ATA (SATA) interface, a SCSI interface, a USB interface, a proprietary interface, or a combination thereof.Disk emulator 160 permits a solid-state drive (SSD) 164 to be connected toinformation handling system 100 via anexternal interface 162. An example ofexternal interface 162 includes a USB interface, an IEEE 1394 (Firewire) interface, a proprietary interface, or a combination thereof. Alternatively, SSD 164 can be disposed withininformation handling system 100. - I/
O interface 170 includes aperipheral interface 172 that connects I/O interface 170 to add-onresource 174, to TPM 176, and tonetwork interface device 180.Peripheral interface 172 can be the same type of interface as I/O channel 112, or can be a different type of interface. As such, I/O interface 170 extends the capacity of I/O channel 112 whenperipheral interface 172 and the I/O channel are of the same type, and the I/O interface translates information from a format suitable to the I/O channel to a format suitable to theperipheral channel 172 when they are of a different type. Add-onresource 174 can include a sound card, data storage system, an additional graphics interface, another add-on resource, or a combination thereof. Add-onresource 174 can be on a main circuit board, a separate circuit board or an add-in card disposed withininformation handling system 100, a device that is external to the information handling system, or a combination thereof. -
Network interface device 180 represents a network communication device disposed withininformation handling system 100, on a main circuit board of the information handling system, integrated onto another element such aschipset 110, in another suitable location, or a combination thereof.Network interface device 180 includes anetwork channel 182 that provides an interface to devices that are external toinformation handling system 100. In a particular embodiment,network channel 182 is of a different type thanperipheral channel 172 andnetwork interface device 180 translates information from a format suitable to the peripheral channel to a format suitable to external devices. In a particular embodiment,network interface device 180 includes a host bus adapter (HBA), a host channel adapter, a network interface card (NIC), or other hardware circuit that can connect the information handling system to a network. An example ofnetwork channel 182 includes an InfiniBand channel, a fiber channel, a gigabit Ethernet channel, a proprietary channel architecture, or a combination thereof.Network channel 182 can be connected to an external network resource (not illustrated). The network resource can include another information handling system, a data storage system, another network, a grid management system, another suitable resource, or a combination thereof. - BMC 190 is connected to multiple elements of
information handling system 100 via one or more management interface 192 to provide out of band monitoring, maintenance, and control of the elements of the information handling system. As such, BMC 190 represents a processing device different fromprocessors information handling system 100. In an embodiment, BMC 190 may be responsible for granting access to a remote management system that may establish control of the elements to implement power management, cooling management, storage management, and the like. The BMC 190 may also grant access to an external device. In this case, the BMC may include transceiver circuitry to establish wireless communications with the external device such as a mobile device. The transceiver circuitry may operate on a Wi-Fi channel, a near-field communication (NFC) channel, a Bluetooth or Bluetooth-Low-Energy (BLE) channel, a cellular based interface such as a global system for mobile (GSM) interface, a code-division multiple access (CDMA) interface, a universal mobile telecommunications system (UMTS) interface, a long-term evolution (LTE) interface, another cellular based interface, or a combination thereof. A mobile device may include Ultrabook, a tablet computer, a netbook, a notebook computer, a laptop computer, mobile telephone, a cellular telephone, a smartphone, a personal digital assistant, a multimedia playback device, a digital music player, a digital video player, a navigational device, a digital camera, and the like. - The term BMC may be used in the context of server systems, while in a consumer-level device a BMC may be referred to as an embedded controller (EC). A BMC included at a data storage system can be referred to as a storage enclosure processor. A BMC included at a chassis of a blade server can be referred to as a chassis management controller, and embedded controllers included at the blades of the blade server can be referred to as blade management controllers. Out-of-band communication interfaces between BMC and elements of the information handling system may be provided by management interface 192 that may include an inter-integrated circuit (I2C) bus, a system management bus (SMBUS), a power management bus (PMBUS), a low pin count (LPC) interface, a serial bus such as a universal serial bus (USB) or a serial peripheral interface (SPI), a network interface such as an Ethernet interface, a high-speed serial data link such as PCIe interface, a network controller-sideband interface (NC-SI), or the like. As used herein, out-of-band access refers to operations performed apart from a BIOS/operating system execution environment on
information handling system 100, that is apart from the execution of code byprocessors - In an embodiment, the BMC 190 implements an integrated remote access controller (iDRAC) that operates to monitor and maintain system firmware, such as code stored in BIOS/EFI module 142, option ROMs for
graphics interface 130,disk controller 150, add-onresource 174,network interface 180, or other elements ofinformation handling system 100, as needed or desired. In particular, BMC 190 includes a network interface 194 that can be connected to a remote management system to receive firmware updates, as needed or desired. Here BMC 190 receives the firmware updates, stores the updates to a data storage device associated with the BMC, transfers the firmware updates to NV-RAM of the device or system that is the subject of the firmware update, thereby replacing the currently operating firmware associated with the device or system, and reboots information handling system, whereupon the device or system utilizes the updated firmware image. - BMC 190 utilizes various protocols and application programming interfaces (APIs) to direct and control the processes for monitoring and maintaining the system firmware. An example of a protocol or API for monitoring and maintaining the system firmware includes a graphical user interface (GUI) associated with BMC 190, an interface defined by the Distributed Management Taskforce (DMTF) (such as Web Services Management (WS-MAN) interface, a Management Component Transport Protocol (MCTP) or, Redfish interface), various vendor defined interfaces (such as Dell EMC Remote Access Controller Administrator (RACADM) utility, Dell EMC Open Manage Server Administrator (OMSS) utility, Dell EMC Open Manage Storage Services (OMSS) utility, Dell EMC Open Manage Deployment Toolkit (DTK) suite), representational state transfer (REST) web API, a BIOS setup utility such as invoked by a “F2” boot option, or another protocol or API, as needed or desired.
- In a particular embodiment, BMC 190 is included on a main circuit board (such as a baseboard, a motherboard, or any combination thereof) of
information handling system 100, or is integrated into another element of the information handling system such aschipset 110, or another suitable element, as needed or desired. As such, BMC 190 can be part of an integrated circuit or a chip set withininformation handling system 100. BMC 190 may operate on a separate power plane from other resources ininformation handling system 100. Thus BMC 190 can communicate with the remote management system via network interface 194 or the BMC can communicate with the external mobile device using its own transceiver circuitry while the resources or elements ofinformation handling system 100 are powered off or at least in low power mode. Here, information can be sent from the remote management system or external mobile device to BMC 190 and the information can be stored in a RAM or NV-RAM associated with the BMC. Information stored in the RAM may be lost after power-down of the power plane for BMC 190, while information stored in the NV-RAM may be saved through a power-down/power-up cycle of the power plane for the BMC. - In a typical usage case,
information handling system 100 represents an enterprise class processing system, such as may be found in a datacenter or other compute-intense processing environment. Here, there may be hundreds or thousands of other enterprise class processing systems in the datacenter. In such an environment, the information handling system may represent one of a wide variety of different types of equipment that perform the main processing tasks of the datacenter, such as modular blade servers, switching and routing equipment (network routers, top-of-rack switches, and the like), data storage equipment (storage servers, network attached storage, storage area networks, and the like), or other computing equipment that the datacenter uses to perform the processing tasks. - For purposes of this disclosure
information handling system 100 can include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes. For example,information handling system 100 can be a personal computer, a laptop computer, a smart phone, a tablet device or other consumer electronic device, a network server, a network storage device, a switch router or other network communication device, or any other suitable device and may vary in size, shape, performance, functionality, and price. Further,information handling system 100 can include processing resources for executing machine-executable code, such as a central processing unit (CPU), a programmable logic array (PLA), an embedded device such as a System-on-a-Chip (SoC), or other control logic hardware.Information handling system 100 can also include one or more computer-readable medium for storing machine-executable code, such as software or data. Additional components ofinformation handling system 100 can include one or more storage devices that can store machine-executable code, one or more communications ports for communicating with external devices, and various input and output (I/O) devices, such as a keyboard, a mouse, and a video display.Information handling system 100 can also include one or more buses operable to transmit information between the various hardware components. -
FIGS. 2-3 illustrate ahost memory buffer 200, according to exemplary embodiments. Thehost memory buffer 200 may be any portion of thememory 120 that is configured for, and/or dedicated to, the solid-state drive (SSD) 164. When theprocessors 102/104 access and/or execute an operating system 202 (perhaps stored by the memory 120), theoperating system 202 may allocate and/or partition thehost memory buffer 200 to the solid-state drive 164. The solid-state drive 164 may have exclusive use of thehost memory buffer 200, or thehost memory buffer 200 may be a shared resource with other components, peripherals, or software/services. Even though the solid-state drive 164 may have its own internal processor and memory device (not shown for simplicity), thehost memory buffer 200 may increase speed and efficiency for some input/output tasks. Thehost memory buffer 200 takes advantage of the I/O channel 112 (such as the direct memory access capabilities of PCI Express) to allow the solid-state drive 164 to access and use any of the memory 120 (such as DRAM). -
FIG. 3 illustrates thehost memory buffer 200 as acache memory 204. Conventional schemes utilize thehost memory buffer 200 to cache mapping information (such as a mapping table of logical block addresses to physical NAND addresses). This disclosure, though, uses thehost memory buffer 200 as write cache for read prioritization. Because the size of thehost memory buffer 200 is substantially greater (i.e., 60 times larger) than the conventional cache internal to the solid-state drive 164, thehost memory buffer 200 may efficiently be used to prioritize read requests oroperations 206 over write requests oroperations 208 in a typical client busty workload patterns. When the host (such as the information handling system 100) issues read and writerequests state drive 164 may re-schedule anywrite operation 208 from its internal cache to thehost memory buffer 200. The solid-state drive 164 may thus prioritize the readoperation 206 without first completing and/or executing thewrite operation 208. This caching strategy extracts maximum potential read write performance in typical mixed workload conditions. -
FIGS. 4-7 illustrate the caching strategy, according to exemplary embodiments.FIGS. 4-5 illustrate read/write bottlenecks. When theinformation handling system 100 issues or sends a mixed sequence of the readoperations 206 and thewrite operations 208, a new or recent read request oroperation 206 is blocked, or delayed, by a prior or historical write request oroperation 208 that is currently being executed. The readrequest 206, in other words, may be substantially delayed until thewrite request 208 is completed. The mixed sequence (of the readoperations 206 and the write operations 208) thus causes a software program to be delayed. Data writes, in other words, may require longer times than data reads. When the software program is in process at the component media (such as the solid-state drive 164), anyread operation 206 has to be waited until NAND media completes thewrite operation 208.FIG. 5 illustrates this read/write performance limitation by charting NVMe SSD performance in different ratios of read and write I/O, swinging from 100% read to 100% write in mixed manner (tested with Hynix PC400 512 GB, 4 KB random read/write mixed atQueue Depth 4, at 8 GB range). When the read and write mixed ratio is 75% and 25%, the combined performance is about thirty percent (30%) less than ideally perform based on its raw read (100%) and write numbers. Real life workloads are always mixture of random read/write operations. So, the real-life benchmark numbers such as PCMark are often less than those synthetic benchmark numbers for today's SSDs. -
FIGS. 6-7 , though, illustrate prioritization. When the solid-state drive 164 receives anywrite request 208,FIG. 6 illustrates the solid-state drive 164 suspending execution of thewrite request 208. The solid-state drive 164, instead, may send and/or cache thewrite request 208 to thehost memory buffer 200. Because the controller of the solid-state drive 164 need not immediately execute thewrite request 208, the solid-state drive 164 may ignore or defer thewrite request 208 and, instead, prioritize the readrequest 206 over thewrite request 208. The solid-state drive 164 may thus consult any mapping table or information, retrieve the corresponding data blocks to the read, and return send the data blocks to the hostinformation handling system 100 in response to the readrequest 206. AsFIG. 7 illustrates, when the solid-state drive 164 is idle (perhaps when all pending read requests 206 have been completed), the controller of the solid-state drive 164 may begin executing a queue of the write requests 208. The solid-state drive 164 may thus begin retrieving and executing the queuedwrite requests 208 that were previously cached to thehost memory buffer 200. The solid-state drive 164 thus flushes the pending write requests 208 in any order (such as chronological FIFO or LIFO). As eachwrite request 208 is completed, the solid-state drive 164 may update any mapping table or information with logical and physical addresses. Should the solid-state drive 164 receive another or interveningread request 206, thesolid state drive 164 may again suspend or defer the remaining cache of the write requests 208 stored in thehost memory buffer 200. -
FIGS. 8-9 illustrate performance improvements, according to exemplary embodiments. Because theread operation 206 is prioritized, machine performance and the user's experience are enhanced. Thehost memory buffer 200 optimizes the input/output schedule in real life mixed IO scenarios. Any trace-based benchmark will result up to 30% better performance using the same SSD hardware. There is no additional cost since it is device firmware implementation.FIGS. 8-9 thus illustratePC Mark 8 benchmarking (trace-based) analysis and simulation results. Real life workload consists of small payload sizes, with 4 KB is the highest used payload size. Access patterns are mixture of read and write (80% reads and 20% writes). Most of queue depths are low (less than 4), and 95% of the queue depths are less than eight (8). AsFIG. 9 shows, the solid-state drive 164 with thehost memory buffer 200 for write cache plus read prioritization boosts the performance of the same drive by 5%. The early simulated performance result is only able to prioritized 10% of potential read in the mixed workload. With further optimization, it can help to boost the performance up to 30%. This means that the write caching strategy differentiates system performance by 30% at the same hardware configuration. - Exemplary embodiments thus present an elegant solution. The solid-
state drive 164 may suspend execution of anywrite request 208 and, instead, send or cache thewrite request 208 to thehost memory buffer 200. The solid-state drive 164 may thus prioritize the readrequest 206 for relatively immediate response. Should no readrequests 206 be pending, the solid-state drive 164 may then change its caching strategy and begin executing the queue of the write requests 208 stored in thehost memory buffer 200. A thirty percent (30%) improvement in drive performance may result. -
FIG. 10 illustrates a method or algorithm for caching to thehost memory buffer 200, according to exemplary embodiments. The hostinformation handling system 100 sends a sequence of input/output requests to the solid-state drive 164 (Block 220). The byte sizes of any of input/output requests (such as theread operation 206 and/or the write operation 208) are compared to a threshold size (such as 16 KB). If the payload sizes of the input/output requests fail to satisfy the threshold size (Block 222), then the input/output requests (such as read commands 206 and/or the write commands 208) are queued/scheduled (Block 224) and executed (Block 226). While the threshold size may be configurable to suit performance and memory objectives, large payloads (such as greater than the 16 KB) may be unsuited for smaller sizes of the host memory buffer 200 (such as 64 MB). However, should the payload sizes of the input/output requests satisfy the threshold size (Block 222), then the amount of the data to be written (as described or specified by the write request 208) is compared to the byte size of thehost memory buffer 200. If the amount of the data to be written is less than size of the host memory buffer 200 (Block 228), then the read requests 206 may be split from the write requests 208 and sequentially queued (Block 230). The write requests 208 are written and queued to the host memory buffer 200 (Block 232). However, if the amount of the data to be written is greater than size of the host memory buffer 200 (Block 228), then the write requests 208 are written and queued to the host memory buffer 200 (Block 232). When the readrequests 206 are completed, the queued write requests 208 (in the host memory buffer 200) are flushed and written to the NAND of the solid-state drive 164 (Block 234). - Although only a few exemplary embodiments have been described in detail herein, those skilled in the art will readily appreciate that many modifications are possible in the exemplary embodiments without materially departing from the novel teachings and advantages of the embodiments of the present disclosure. Accordingly, all such modifications are intended to be included within the scope of the embodiments of the present disclosure as defined in the following claims. In the claims, means-plus-function clauses are intended to cover the structures described herein as performing the recited function and not only structural equivalents.
- Devices, modules, resources, or programs that are in communication with one another need not be in continuous communication with each other, unless expressly specified otherwise. In addition, devices, modules, resources, or programs that are in communication with one another can communicate directly or indirectly through one or more intermediaries.
- The above-disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover any and all such modifications, enhancements, and other embodiments that fall within the scope of the present invention. Thus, to the maximum extent allowed by law, the scope of the present invention is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/794,404 US11093174B1 (en) | 2020-02-19 | 2020-02-19 | Information handling system having improved host memory buffer for input/output requests |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/794,404 US11093174B1 (en) | 2020-02-19 | 2020-02-19 | Information handling system having improved host memory buffer for input/output requests |
Publications (2)
Publication Number | Publication Date |
---|---|
US11093174B1 US11093174B1 (en) | 2021-08-17 |
US20210255801A1 true US20210255801A1 (en) | 2021-08-19 |
Family
ID=77273475
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/794,404 Active US11093174B1 (en) | 2020-02-19 | 2020-02-19 | Information handling system having improved host memory buffer for input/output requests |
Country Status (1)
Country | Link |
---|---|
US (1) | US11093174B1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114554126A (en) * | 2022-01-29 | 2022-05-27 | 山东云海国创云计算装备产业创新中心有限公司 | Substrate management control chip, video data transmission method and server |
US20220171571A1 (en) * | 2020-11-27 | 2022-06-02 | SK Hynix Inc. | Memory system and operating method thereof |
WO2023086127A1 (en) * | 2021-11-15 | 2023-05-19 | Western Digital Technologies, Inc. | Host memory buffer cache management |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114153768A (en) * | 2021-11-26 | 2022-03-08 | 山东云海国创云计算装备产业创新中心有限公司 | Data transmission method, device, equipment and computer readable storage medium |
US11829642B2 (en) | 2021-11-30 | 2023-11-28 | Red Hat, Inc. | Managing write requests for drives in cloud storage systems |
US11816035B2 (en) * | 2021-12-21 | 2023-11-14 | Micron Technology, Inc | Latency reduction using stream cache |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9934151B2 (en) | 2016-06-28 | 2018-04-03 | Dell Products, Lp | System and method for dynamic optimization for burst and sustained performance in solid state drives |
US10255177B2 (en) | 2016-10-10 | 2019-04-09 | Dell Products, Lp | System and method for adaptive optimization for performance in solid state drives based on read/write intensity |
US20180349287A1 (en) | 2017-06-02 | 2018-12-06 | Dell Products L.P. | Persistent Storage Device Information Cache |
US10409739B2 (en) * | 2017-10-24 | 2019-09-10 | Micron Technology, Inc. | Command selection policy |
KR20190090614A (en) * | 2018-01-25 | 2019-08-02 | 에스케이하이닉스 주식회사 | Memory controller and operating method thereof |
US11144240B2 (en) * | 2018-08-24 | 2021-10-12 | Micron Technology, Inc. | Memory sub-system for increasing bandwidth for command scheduling |
-
2020
- 2020-02-19 US US16/794,404 patent/US11093174B1/en active Active
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20220171571A1 (en) * | 2020-11-27 | 2022-06-02 | SK Hynix Inc. | Memory system and operating method thereof |
US11775214B2 (en) * | 2020-11-27 | 2023-10-03 | SK Hynix Inc. | Memory system for suspending and resuming execution of command according to lock or unlock request, and operating method thereof |
WO2023086127A1 (en) * | 2021-11-15 | 2023-05-19 | Western Digital Technologies, Inc. | Host memory buffer cache management |
US11853603B2 (en) | 2021-11-15 | 2023-12-26 | Western Digital Technologies, Inc. | Host memory buffer cache management |
CN114554126A (en) * | 2022-01-29 | 2022-05-27 | 山东云海国创云计算装备产业创新中心有限公司 | Substrate management control chip, video data transmission method and server |
Also Published As
Publication number | Publication date |
---|---|
US11093174B1 (en) | 2021-08-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11093174B1 (en) | Information handling system having improved host memory buffer for input/output requests | |
US11036667B2 (en) | System and method to scale baseboard management controller management of storage instrumentation | |
US10990562B2 (en) | System and method of asymmetric system description for optimized scheduling | |
US9477485B2 (en) | Optimizing computer hardware usage in a computing system that includes a plurality of populated central processing unit (‘CPU’) sockets | |
US10802760B2 (en) | Apparatus and method of intelligent dynamic application aware storage device optimization | |
US11442885B2 (en) | System and method to change field-programmable gate array personality from a baseboard management controller | |
US20210041933A1 (en) | System and Method for Power Management of Field-Programmable Gate Arrays and Load Balancing of Personality Bitstreams from a Baseboard Management Controller | |
US20220300448A1 (en) | Peripheral component interconnect express device and method of operating the same | |
US10853255B2 (en) | Apparatus and method of optimizing memory transactions to persistent memory using an architectural data mover | |
US10102135B2 (en) | Dynamically-adjusted host memory buffer | |
US10649943B2 (en) | System and method for I/O aware processor configuration | |
US11663021B2 (en) | System and method for providing granular processor performance control | |
US11405330B2 (en) | System and method for bandwidth optimization with support for multiple links | |
US11061838B1 (en) | System and method for graphics processing unit management infrastructure for real time data collection | |
US11212375B2 (en) | System and method to provide heterogeneous protocols on network interface devices | |
US11513575B1 (en) | Dynamic USB-C mode configuration | |
US11755518B2 (en) | Control of Thunderbolt/DisplayPort multiplexor for discrete USB-C graphics processor | |
US10942766B2 (en) | System and method for providing heterogeneous personality bitstreams on field-programmable gate arrays from a baseboard management controller | |
US20230064833A1 (en) | Ensuring key event delivery to a host from a client during a high event rate | |
US20240028558A1 (en) | Disabling processor cores for best latency in a multiple core processor | |
US20220269797A1 (en) | System and method for secure movement of trusted memory regions across numa nodes | |
US20240028201A1 (en) | Optimal memory tiering of large memory systems using a minimal number of processors | |
US20240118903A1 (en) | Power conservation and standby graphics rendering in an information handling system | |
US20240028344A1 (en) | Core mapping based on latency in a multiple core processor | |
US20220124164A1 (en) | System and method to offload point to multipoint transmissions |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., TEXAS Free format text: SECURITY AGREEMENT;ASSIGNORS:CREDANT TECHNOLOGIES INC.;DELL INTERNATIONAL L.L.C.;DELL MARKETING L.P.;AND OTHERS;REEL/FRAME:053546/0001 Effective date: 20200409 |
|
AS | Assignment |
Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, NORTH CAROLINA Free format text: SECURITY AGREEMENT;ASSIGNORS:DELL PRODUCTS L.P.;EMC IP HOLDING COMPANY LLC;REEL/FRAME:052771/0906 Effective date: 20200528 |
|
AS | Assignment |
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT, TEXAS Free format text: SECURITY INTEREST;ASSIGNORS:DELL PRODUCTS L.P.;EMC IP HOLDING COMPANY LLC;THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:052851/0081 Effective date: 20200603 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT, TEXAS Free format text: SECURITY INTEREST;ASSIGNORS:DELL PRODUCTS L.P.;EMC IP HOLDING COMPANY LLC;REEL/FRAME:052851/0917 Effective date: 20200603 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT, TEXAS Free format text: SECURITY INTEREST;ASSIGNORS:DELL PRODUCTS L.P.;EMC IP HOLDING COMPANY LLC;REEL/FRAME:052852/0022 Effective date: 20200603 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT, TEXAS Free format text: SECURITY INTEREST;ASSIGNORS:DELL PRODUCTS L.P.;EMC CORPORATION;EMC IP HOLDING COMPANY LLC;REEL/FRAME:053311/0169 Effective date: 20200603 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: EMC IP HOLDING COMPANY LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST AT REEL 052771 FRAME 0906;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058001/0298 Effective date: 20211101 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST AT REEL 052771 FRAME 0906;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058001/0298 Effective date: 20211101 |
|
AS | Assignment |
Owner name: EMC IP HOLDING COMPANY LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053311/0169);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:060438/0742 Effective date: 20220329 Owner name: EMC CORPORATION, MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053311/0169);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:060438/0742 Effective date: 20220329 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053311/0169);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:060438/0742 Effective date: 20220329 Owner name: EMC IP HOLDING COMPANY LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (052851/0917);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:060436/0509 Effective date: 20220329 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (052851/0917);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:060436/0509 Effective date: 20220329 Owner name: EMC IP HOLDING COMPANY LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (052851/0081);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:060436/0441 Effective date: 20220329 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (052851/0081);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:060436/0441 Effective date: 20220329 Owner name: EMC IP HOLDING COMPANY LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (052852/0022);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:060436/0582 Effective date: 20220329 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (052852/0022);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:060436/0582 Effective date: 20220329 |