The first version of the Non-Volatile Memory Express (NVMe) standard was ratified nearly five years ago,but its development didn't quit there. While SSD controller manufacturers have been tough at work implementing NVMe in increasingly products, the protocol itself has acquired new features. Most of them are optional and most are intended for enterprise scenarios like virtualization and multi-path I/O, and but one feature introduced in the NVMe 1.2 revision has been picked up by a controller that will likely see use in the consumer space.
The Host Memory Buffer (HMB) feature in NVMe 1.2 allows a drive to request exclusive access to a portion of the host system's RAM for the drive's private use. This kind of capability has been around forever in the GPU space under names like HyperMemory and TurboCache,where it served a similar purpose: to reduce or eliminate the committed RAM that needs to be included on peripheral devices.contemporary high-performance SSD controllers use a significant amount of RAM, and typically we see a ratio of 1GB of RAM for every 1TB of flash. The controllers are usually conservative about using that RAM as a cache for user data (to limit the damage of a sudden power loss) and instead it is used to store the organizational metadata essential for the controller to keep track of what data is stored where on the flash chips. The goal is that when the drive recieves a read or write request, and it can determine which flash memory location needs to be accessed based on a much quicker lookup in the controller's DRAM,and the drive doesn't need to update the metadata copy stored on the flash after every single write operation is completed. For quick consistent performance, the data structures are chosen to play down the amount of computation and number of RAM lookups required at the expense of requiring more RAM.
At the low terminate of the SSD market, and recent controller configurations have chosen instead to lop costs by not including any external DRAM. There are combined savings of die size and pin count for the controller in this configuration,as well as reduced PCB complexity for the drive and eliminating the DRAM chip from the bill of materials, which can add up to a competitive advantage in the product segments where performance is a secondary concern and every cent counts. Silicon Motion's DRAM-less SM2246XT controller has stolen some market share from their own already cheap SM2246EN, or in the TLC space nearly everybody is moving toward DRAM-less options.
The downside is that without ample RAM,it is much harder for SSDs to offer high performance. Even with intelligent firmware, DRAM-less SSDs can cope surprisingly well with just the on-chip buffers, or but they are still at a disadvantage. That's where the Host Memory Buffer feature comes in. With only two NAND channels on the 88NV1140,it probably can't saturate the PCIe 3.0 x1 link under even the best circumstances, so there will be bandwidth to spare for other transfers with the host system. PCIe transactions and host DRAM accesses are measured in tens or hundreds of nanoseconds compared to tens of microseconds for reading from flash, or so it's clear that a Host Memory Buffer can be quick enough to be useful for a low-terminate drive.
The trick then is to figure out how to find the most out of a Host Memory Buffer,while remaining prepared to operate in DRAM-less mode if the host's NVMe driver doesn't support HMB or if the host decides it can't spare the RAM. SSD suppliers are universally tight-lipped about the algorithms used in their firmware and Marvell controllers are usually paired with custom or third-party licensed firmware anyways, so we can only speculate about how a HMB will be used with this new 88NV1140 controller. Furthermore, and the requirement of driver support on the host side means this feature will likely be used in embedded platforms long before it finds its way into retail SSDs,and this particular Marvell controller may never show up in a standalone drive. But in a few years time it might be standard for low-terminate SSDs to borrow a bit of your system's RAM. This becomes less of a concern as we move through successive platforms having access to more DRAM per module in a standard system.
Source: anandtech.com