{"id":29970,"date":"2021-08-09T08:00:41","date_gmt":"2021-08-09T15:00:41","guid":{"rendered":"https:\/\/phisonblog.com\/?p=29970"},"modified":"2025-07-21T18:20:00","modified_gmt":"2025-07-22T01:20:00","slug":"key-features-available-with-nvme-2-0-ssd-2","status":"publish","type":"post","link":"https:\/\/phisonblog.com\/ko\/key-features-available-with-nvme-2-0-ssd-2\/","title":{"rendered":"NVMe 2.0 SSD\uc5d0\uc11c \uc0ac\uc6a9\ud560 \uc218 \uc788\ub294 \uc8fc\uc694 \uae30\ub2a5"},"content":{"rendered":"

[et_pb_section fb_built=”1″ _builder_version=”4.16″ _module_preset=”default” custom_margin=”0px||||false|false” custom_padding=”0px||||false|false” global_colors_info=”{}”][et_pb_row _builder_version=”4.16″ _module_preset=”default” width=”100%” max_width=”100%” custom_margin=”||||false|false” custom_padding=”0px||||false|false” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.16″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.16″ _module_preset=”default” ul_text_align=”right” ul_line_height=”1.7em” global_colors_info=”{}”]<\/p>\n

<\/p>\n

The NVM Express\u00ae (NVMe\u00ae) interface allows host software to communicate with a non-volatile memory subsystem. It defines the protocol and boosts the performance of PCIe NVMe SSDs.<\/p>\n

In June 2021, NVMe 2.0 was released<\/a>, standardizing some extra features and improvements, especially for data centers. But the most significant change is the “refactoring”, in which NVM Express restructured the original NVMe1.4, NVMe-MI, and NVMe-oF to make the newest NVMe specification more scalable and extensible.<\/p>\n

 <\/p>\n

\"\"<\/a>
Read: Best Practices in NVMe Power Management<\/div><\/div><\/div><\/div><\/div>\n

 <\/p>\n

\"\"<\/a><\/p>\n

\u00a0<\/h4>\n

NVMe 2.0 refactoring<\/h3>\n

The scale of the latest NVMe refactoring is why this release is numbered 2.0 instead of 1.5. The refactoring included in NVMe 2.0 enables faster and simpler development of NVMe solutions to support the increasingly diverse NVMe device environment.<\/p>\n

The previous version included the NVMe 1.4 base spec, NVMe-MI, and NVMe-Of specs. However, the latest NVMe 2.0 library of specifications comprises four groups of specs with a total of eight documents:<\/p>\n

1. NVMe base specification<\/strong><\/p>\n

\u2022 NVMe Base specification<\/p>\n

2. Separate specifications per command set<\/strong><\/p>\n

\u2022 NVM Command Set specification
\u2022 Zoned Namespace Command Set specification
\u2022 Key-Value Command Set specification<\/p>\n

3. Modular transport mapping layer<\/strong><\/p>\n

\u2022 PCIe Transport specification
\u2022 RDMA Transport specification
\u2022 TCP Transport specification<\/p>\n

4. NVMe Management Interface<\/strong><\/p>\n

\u2022 NVMe-MI<\/p>\n

The refactoring in NVMe 2.0 includes integrating the NVMe and NVMe over Fabrics (NVMe-oF) specifications and creating separate specifications per command set and per transport mapping layers. For example, PCIe has been broken out into one transport specification.<\/p>\n

 <\/p>\n

\"\"<\/a><\/p>\n

\"\"<\/a><\/p>\n

 <\/p>\n

Key features in NVMe 2.0<\/h3>\n

Besides refactoring and releasing sequestered technical proposals from previous specifications, the NVMe 2.0 family of specifications includes four critical features.<\/p>\n

\u00a0<\/h3>\n

Zoned Namespaces (ZNS)<\/h3>\n

This feature provides the interface that allows NVMe SSD and host to collaborate on data placement. It can align the data to the physical media of the SSD, improving overall performance and increasing the capacity that can be exposed to the host. More than that, write amplification is significantly improved with ZNS. In other words, the use of ZNS can extend the lifespan of NVMe SSDs.<\/p>\n

The Zoned Namespace Command Set specification defines how ZNS SSDs can be operated. Three important ZNS SSD’s operational characteristics are:<\/p>\n

1. Zoned Namespace is divided into a set of equally sized zones, which are contiguous non-overlapping ranges of logical block addresses.
2. Writes within a zone must be sequential and start from the position of “Write Pointer”.
3. Each zone must be erased before it can be rewritten.<\/p>\n

 <\/p>\n

\"\"<\/a><\/p>\n

 <\/p>\n

Key-value command set<\/h3>\n

The burst of unstructured data created after the late 2000s boosted the development of the non-relational database. A key-value database is a type of non-relational database that uses a simple key-value method to store data. Both keys and values can be anything. This type of database is highly distributed and allows horizontal scaling at scales that other types of databases cannot achieve. However, organizing data into Log-structured merge-tree (LSMT) may be required in a key-value database. This operation involves much more write cycles in addition to the original data writes and results in a shorter lifetime of an SSD.<\/p>\n

NVMe-KV was developed to solve this problem. It allows access to the data on an NVMe SSD namespace using a key rather than a logical block address. The NVMe-KV Command Set provides the key to store a corresponding value on non-volatile media, then retrieves that value from the media by specifying the corresponding key. By following the NVMe-KV Command Set and Key-Value Storage API Specification defined by SNIA, the KV SSD allows users to access key-value data without the costly and time-consuming overhead of additional translation tables between keys and logical blocks [4].<\/p>\n

 <\/p>\n

\"\"<\/a><\/p>\n

 <\/p>\n

NVMe Endurance Group Management<\/h3>\n

NVMe Endurance Group Management allows media to be configured into Endurance Groups and NVM sets. This enables granularity of access to the SSD and improved control.<\/p>\n

Endurance Group and NVM sets were first introduced in NVMe 1.4, but customers had limited capability to configure them. The configuration would either need to be hard-coded in the drive’s firmware or handled with vendor-specific commands. NVMe 2.0 provides a mechanism for users to allocate the Endurance Group and NVM sets. With more configurable parameters, the NVM subsystem can have more flexibility to isolate the I\/O performance effects and wear-leveling operation of different users on shared drives or arrays.<\/p>\n

This diagram shows the NVMe Storage Entity Hierarchy:<\/p>\n

1. NVM subsystem contains domains
2. Domains contain endurance groups
3. Endurance Groups contain NVM Sets
4. NVM sets contain Namespaces
5. Namespaces contain an array of logical blocks<\/p>\n

 <\/p>\n

\"\"<\/a><\/p>\n

 <\/p>\n

HDD (rotational media) now supported with NVMe 2.0<\/h3>\n

Although the SATA specification has not been updated for 12 years, HDDs still cannot approach the theoretical bandwidth of SATA interface (600MB\/s). So we don’t expect the Rotational Media support of NVMe 2.0 will bring immediate benefit to the HDDs in terms of performance. The key reason NVMe supports Rotational Media is to improve overall system composability. A highly composable system provides components that can be selected and assembled in various combinations to satisfy specific user requirements. This feature is something that will benefit the data center and enterprise environments.<\/p>\n

 <\/p>\n

\"\"<\/a><\/p>\n

 <\/p>\n

NVMe 2.0 is a significant improvement over 1.4<\/h3>\n

Looking at the new features in NVMe 2.0, it’s clear that NVMe is now focusing on the demand from enterprises and data centers. The result is not a surprise at all. Just as Jeff Janukowicz, Research Vice President IDC, said: “NVMe technology is the leading interface for SSDs, with overall worldwide enterprise SSD capacity expected to grow at a 43% compound annual growth rate into 2024. NVMe architecture is designed for future SSD development and form factors, as we enter a new era in hyper-scale and enterprise computing that drives digital transformation.”<\/p>\n

 <\/p>\n

\n

\u00a0<\/h4>\n

Resources used in this article:<\/h4>\n

1. Figure 1,2,6: \u00a0NVM Express<\/a>
2. Figure 3: \u00a0Zone Storage<\/a>
3. Figure 4: \u00a0Northeastern University College of Engineering<\/a>
4 Figure. 5: \u00a0NVM Express<\/a><\/p>\n

 <\/p>\n

\"\"<\/a>
Read: AHCI vs. NVMe<\/div><\/div><\/div><\/div><\/div>\n

 <\/p>\n

 <\/p>\n

\n
\n
0 Links<\/div>\n<\/div>\n

<\/p>\n<\/div>\n

[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.16″ _module_preset=”default” width=”100%” max_width=”100%” custom_margin=”||||false|false” custom_padding=”0px||||false|false” saved_tabs=”all” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.16″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

Frequently Asked Questions (FAQ) :<\/strong><\/h3>\n

[\/et_pb_text][et_pb_toggle _builder_version=”4.27.4″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” theme_builder_area=”post_content” title=”What makes NVMe 2.0 different from NVMe 1.4?” sticky_enabled=”0″]<\/p>\n

NVMe 2.0 introduces modular refactoring that separates command sets and transport layers for easier integration and scalability. It also brings key enterprise-ready features like Zoned Namespace support, Key-Value storage, and dynamic Endurance Group configuration<\/span>, <\/span>providing better resource isolation and system composability.<\/span><\/p>\n

[\/et_pb_toggle][et_pb_toggle _builder_version=”4.27.4″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” theme_builder_area=”post_content” title=”How does Zoned Namespace (ZNS) improve SSD performance and endurance?” sticky_enabled=”0″]<\/p>\n

ZNS aligns data with physical media layout, minimizing write amplification. Data must be written sequentially within zones, and zones must be erased before reuse<\/span>, <\/span>this<\/span> reduces internal overhead, boosts performance, and significantly extends drive lifespan, making it ideal for write-heavy workloads.<\/span><\/p>\n

[\/et_pb_toggle][et_pb_toggle _builder_version=”4.27.4″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” theme_builder_area=”post_content” title=”Why is Key-Value (KV) storage relevant in NVMe 2.0?” sticky_enabled=”0″]<\/p>\n

KV storage addresses inefficiencies in handling unstructured data by enabling direct key-based access, removing the need for traditional block address translation. This is especially beneficial for NoSQL databases and high-scale, low-latency environments where performance and SSD longevity are critical.<\/span><\/span><\/p>\n

[\/et_pb_toggle][et_pb_toggle _builder_version=”4.27.4″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” theme_builder_area=”post_content” title=”What does Endurance Group Management offer that wasn’t available in NVMe 1.4?” sticky_enabled=”0″]<\/p>\n

While <\/span>NVMe<\/span> 1.4 introduced the concept, configuration was <\/span>vendor-dependent<\/span>. <\/span>NVMe<\/span> 2.0 standardizes it, allowing users to dynamically create and manage endurance groups and NVM sets. This enhances multi-tenant SSD performance, wear isolation, and drive lifespan across varied workloads.<\/span><\/p>\n

[\/et_pb_toggle][et_pb_toggle _builder_version=”4.27.4″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” theme_builder_area=”post_content” title=”How does NVMe 2.0 align with AI and machine learning workloads?” sticky_enabled=”0″]<\/p>\n

NVMe 2.0 enables fine-grained storage control, low-latency access (via KV), and optimized endurance<\/span>, <\/span>all essential for AI\/ML environments that generate high-throughput, mixed read\/write workloads. Zoned storage and direct key access can also streamline data preprocessing pipelines.<\/span><\/p>\n

[\/et_pb_toggle][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":"

The NVM Express\u00ae (NVMe\u00ae) interface allows host software to communicate with a non-volatile memory subsystem. It defines the protocol and boosts the performance of PCIe NVMe SSDs. In June 2021, NVMe 2.0 was released, standardizing some extra features and improvements, especially for data centers. But the most significant change is the “refactoring”, in which NVM […]<\/p>\n","protected":false},"author":24,"featured_media":33425,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_et_pb_use_builder":"on","_et_pb_old_content":"","_et_gb_content_width":"","inline_featured_image":false,"footnotes":""},"categories":[23,3],"tags":[22],"class_list":["post-29970","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-all-posts","category-enterprise","tag-long-content"],"acf":[],"_links":{"self":[{"href":"https:\/\/phisonblog.com\/ko\/wp-json\/wp\/v2\/posts\/29970","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/phisonblog.com\/ko\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/phisonblog.com\/ko\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/phisonblog.com\/ko\/wp-json\/wp\/v2\/users\/24"}],"replies":[{"embeddable":true,"href":"https:\/\/phisonblog.com\/ko\/wp-json\/wp\/v2\/comments?post=29970"}],"version-history":[{"count":2,"href":"https:\/\/phisonblog.com\/ko\/wp-json\/wp\/v2\/posts\/29970\/revisions"}],"predecessor-version":[{"id":86494,"href":"https:\/\/phisonblog.com\/ko\/wp-json\/wp\/v2\/posts\/29970\/revisions\/86494"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/phisonblog.com\/ko\/wp-json\/wp\/v2\/media\/33425"}],"wp:attachment":[{"href":"https:\/\/phisonblog.com\/ko\/wp-json\/wp\/v2\/media?parent=29970"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/phisonblog.com\/ko\/wp-json\/wp\/v2\/categories?post=29970"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/phisonblog.com\/ko\/wp-json\/wp\/v2\/tags?post=29970"}],"curies":[{"name":"\uc6cc\ub4dc\ud504\ub808\uc2a4","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}