Content deleted Content added
m clean up, added orphan tag, typo(s) fixed: ’s → 's |
added information on nvme and nvme-of that are the emerging block storage protocols. Tags: Reverted Visual edit |
||
Line 25:
Storage blocks are generally accessed by [[iSCSI]], [[Fibre Channel]] or [[Fibre Channel over Ethernet]] (FCoE) protocols. Block storage provides high performance for mission-critical applications and can provide high I/O performance and low latency. it is commonly used in [[Storage area network|Storage Area Network]] environments in place of file storage.
In recent years, with the creation of [[NVM Express|NVMe]] standrard, [https://www.simplyblock.io/nvme-storage NVMe-oF] protocol has gained popularity, in particular driving higher adoption of NVMe/TCP (Non-Volatile Memory Express over TCP).
* NVMe/TCP defines the mapping of NVMe queues, NVMe-oF capsules, and data delivery over the IETF Transport Control Protocol (TCP). This innovative transport protocol offers several advantages:
* NVMe/TCP capitalizes on the inherent low latency of NVMe storage devices. By encapsulating NVMe commands and data within TCP datagrams, it ensures efficient communication between hosts and storage media.
* NVMe/TCP enables a larger number of queues and queue paths for data transport compared to traditional protocols like iSCSI. This scalability results in a significant increase in throughput and a reduction in latency.
* Unlike other NVMe over Fabrics (NVMe-oF) transports, such as NVMe/FC (Fibre Channel), NVMe/TCP runs over Ethernet. This makes it accessible and widely deployable across existing network infrastructures.
Emergence of NVMe-oF standard allows for creation of next-generation [[software-defined storage]] technologies, such as [https://www.simplyblock.io/ simplyblock] that has fully embraced NVMe/TCP as a fundamental component of their container storage system. Leveraging the NVMe/TCP transport, simplyblock provides a seamless and high-performance solution for [[Kubernetes]] environments.
==References==
| |||