Chapter 8 - 14. Congestion Management in TCP Storage Networks

这篇具有很好参考价值的文章主要介绍了Chapter 8 - 14. Congestion Management in TCP Storage Networks。希望对大家有所帮助。如果存在错误或未考虑完全的地方,请大家不吝赐教,您也可以点击"举报违法"按钮提交疑问。

Queue Utilization Considerations

TCP/IP networks typically aim for non-empty queues so that the queues always have packets for transmission without keeping the link idle. This achieves a high transmission rate and returns on investments (cost per Gbps). TCP/IP 网络通常以非空队列为目标,使队列中始终有数据包可供传输,而不会使链路处于空闲状态。这就实现了高传输速率和投资回报(每千兆比特成本)。

As Figure 8-12 shows, non-empty utilization can mean any of the other states—low, high, or even full utilization. In all these states, the link is transmitting at full capacity. But there are some side effects, especially when the queues are highly or fully utilized. 如图 8-12 所示,非空闲利用率可以指任何其他状态--低、高甚至满利用率。在所有这些状态下,链路都是在满负荷传输。但也有一些副作用,尤其是当队列被高度或完全利用时。

Latency

When queue utilization is high, although no packets are dropped, new packets must wait behind the already-queued packets. This significantly affects the completion times of the I/O operations. For example, on a 10 GbE port with 1500-byte frames, if the queue already has 100 packets, the next packet will be delayed by at least 120 microseconds. This is a long time for a packet to spend within a switch, while the All-flash and NVMe storage arrays can achieve I/O completion times in the order of 100s of microseconds. 当队列利用率较高时,虽然不会丢弃数据包,但新数据包必须在已排队的数据包后面等待。这会严重影响 I/O 操作的完成时间。例如,在具有 1500 字节帧的 10 GbE 端口上,如果队列中已经有 100 个数据包,则下一个数据包将至少延迟</文章来源地址https://www.toymoban.com/news/detail-831682.html

到了这里,关于Chapter 8 - 14. Congestion Management in TCP Storage Networks的文章就介绍完了。如果您还想了解更多内容,请在右上角搜索TOY模板网以前的文章或继续浏览下面的相关文章,希望大家以后多多支持TOY模板网!

本文来自互联网用户投稿,该文观点仅代表作者本人,不代表本站立场。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如若转载,请注明出处: 如若内容造成侵权/违法违规/事实不符,请点击违法举报进行投诉反馈,一经查实,立即删除!

领支付宝红包 赞助服务器费用

相关文章

  • Chapter 8 - 13. Congestion Management in TCP Storage Networks

    Switch Buffer Management Recall that during network congestion, a TCP sender relies on the following events for reducing its transmission rate. 回想一下,在网络拥塞期间, TCP 发送端依靠以下事件来降低传输速率。 1. When the sender detects packet loss because of the following reasons. 当发送方因以下原因检测到数据包丢失

    2024年02月21日
    浏览(40)
  • Chapter 8 - 12. Congestion Management in TCP Storage Networks

    Comparison with RoCEv2 Networks RoCEv2 Congestion Management (explained in  Chapter 7 ) uses the same mechanism as ECN in TCP/IP networks. Compare Figure 8-103 with  Figure 7-17  in  Chapter 7 . You can notice that Steps 1 to 4 are the same. The difference is after a destination receives a CE-marked IP packet. RoCEv2 拥塞管理(在第 7 章中解释)

    2024年02月20日
    浏览(39)
  • Chapter 8 - 23. Congestion Management in TCP Storage Networks

    Configuring versus Operating a Shared Storage Network Another important consideration is the operational state of a network. Just because a network is configured for sharing, doesn’t necessarily mean that storage and other traffic flow through it simultaneously. For example, assume you configured a network with 50% bandwidth allocated to iSCSI and NVMe/TCP

    2024年04月09日
    浏览(39)
  • Chapter 8 - 11. Congestion Management in TCP Storage Networks

    Congestion Notification in TCP Storage Networks Congestion Notification in TCP storage networks is achieved by Explicit Congestion Notification (ECN), which is standardized by RFC 3168. As explained earlier, iSCSI and NVMe/TCP layers remain unaware of any such mechanisms. TCP 存储网络中的拥塞通知是通过显式拥塞通知 (ECN) 实现的, RFC 31

    2024年02月20日
    浏览(35)
  • Chapter 7 - 14. Congestion Management in Ethernet Storage Networks以太网存储网络的拥塞管理

    PFC Watchdog PFC watchdog works similarly to Pause timeout, but it only drops the traffic in the queue that is unable to transmit continuously for a timeout duration because of receiving PFC Pause frames. PFC 进程看门狗的工作原理与暂停超时类似,但它只会丢弃队列中因收到 PFC 暂停帧而无法在超时时间内连续传输的流量。

    2024年01月22日
    浏览(49)
  • Chapter 7 - 15. Congestion Management in Ethernet Storage Networks以太网存储网络的拥塞管理

    Congestion Notification in Routed Lossless Ethernet Networks End devices and their applications may not be aware of congestion in the network. A culprit device may continue to send (or solicit) more traffic on the network making the severity of congestion worse or increasing its duration. To solve this problem, the network switches can ‘explicitly’ notif

    2024年01月22日
    浏览(54)
  • chapter14:springboot与安全

    Spring Boot与安全视频 Spring Security, shiro等安全框架。主要功能是”认证“和”授权“,或者说是访问控制。 认证 (Authentication)是建立在一个声明主体的过程(一个主体一般指用户,设备或一些可以在你的应用程序中执行动作的其他系统)。 授权 (Authorization)指确定一个主

    2024年02月14日
    浏览(32)
  • Solidity内存布局介绍 Layout in Memory and Storage

    Solidity reserves four 32-byte slots, with specific byte ranges (inclusive of endpoints) being used as follows: 0x00 - 0x3f (64 bytes): scratch space(暂存空间) for hashing methods  Hash方法的暂存空间. 0x40 - 0x5f (32 bytes): currently allocated memory size (aka. free memory pointer) 0x60 - 0x7f (32 bytes): zero slot Solidity保留了四个32字节的

    2024年02月16日
    浏览(46)
  • 论文笔记-Authenticated Keyword Search in Scalable Hybrid-Storage Blockchains

    混合存储模型: 只有少量meta-data(加密哈希)存在链上,原始数据外包给链下的存储服务商 提出了一个新的ADS 1.首先提出了抑制默克尔倒置(Merkle inv)索引,该索引仅在链上维护部分 ADS 结构,可以使用对数加密证明进行安全更新。 2.提出了一个变色龙倒置(Chameleon inv)索

    2024年01月18日
    浏览(44)
  • 解决RabbitMQ报错Stats in management UI are disabled on this node

    linux 部署 rabbitmq后,打开rabbitmq管理界面。点击channels,会报错 cd /etc/rabbitmq/conf.d/

    2024年02月10日
    浏览(45)

觉得文章有用就打赏一下文章作者

支付宝扫一扫打赏

博客赞助

微信扫一扫打赏

请作者喝杯咖啡吧~博客赞助

支付宝扫一扫领取红包,优惠每天领

二维码1

领取红包

二维码2

领红包