0x13:reports:d2t1t01-nvme-over-tcp-ip
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| 0x13:reports:d2t1t01-nvme-over-tcp-ip [2019/04/10 12:45] – ehalep | 0x13:reports:d2t1t01-nvme-over-tcp-ip [2019/09/28 17:04] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 8: | Line 8: | ||
| This session also covered open-source implementation of NVMe over TCP which has been accepted for upstream. One of the important aspect of NVMe over TCP/IP was mapping of storage IO queues (submission and completion queues) and how they nicely mapped with network IO queues (transmit and receive), which enabled scalability of storage traffic using network IO queues. Essentially in other words, network IO queues are increasing to keep up with multi-core and likewise storage queues are also increasing with flashed storage devices such as NVMe. Hence this protocol enabled the best use of both queueing model (network and storage). | This session also covered open-source implementation of NVMe over TCP which has been accepted for upstream. One of the important aspect of NVMe over TCP/IP was mapping of storage IO queues (submission and completion queues) and how they nicely mapped with network IO queues (transmit and receive), which enabled scalability of storage traffic using network IO queues. Essentially in other words, network IO queues are increasing to keep up with multi-core and likewise storage queues are also increasing with flashed storage devices such as NVMe. Hence this protocol enabled the best use of both queueing model (network and storage). | ||
| - | Site: https:// | + | Site: https:// |
0x13/reports/d2t1t01-nvme-over-tcp-ip.txt · Last modified: 2019/09/28 17:04 by 127.0.0.1