Chapter 8 - 11. Congestion Management in TCP Storage Networks

这篇具有很好参考价值的文章主要介绍了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 3168 对其进行了标准化。如前所述,iSCSI NVMe/TCP 层仍未意识到任何此类机制。

Solution Components

The success of the approach to congestion prevention by notifying the end devices depends upon the following factors: 通过通知终端设备来防止拥塞的方法是否成功取决于以下因素:

1. Congestion detection: A switch (or router) must be able to detect the symptoms of congestion. 交换机(或路由器)必须能够检测到拥塞症状。

2. Sending a notification: After detecting congestion, the switch must be able to inform the end devices about it. 检测到拥塞后,交换机必须能够将拥塞情况通知终端设备。

3. Receiving a notification: The end devices must be able to understand the notification from the switches. 终端设备必须能够理解交换机发出的通知。

4. Congestion prevention action: After being notified about congestion in the network the most important component is for the end devices to take preventive actions, such as reducing their rate. 在收到网络拥塞通知后,最重要的是终端设备采取预防措施,如降低速率。

These are the same components as for Fibre Channel fabrics (explained in Chapter 6) and RoCEv2 networks (explained in Chapter 7). The following sections explain Explicit Congestion Notification in TCP/IP networks using the same components to make it easy to compare the implementation among different transport types and for the users to have a consistent detection and troubleshooting workflow. 文章来源地址https://www.toymoban.com/news/detail-830007.html

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

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

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

相关文章

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

    iSCSI and NVMe/TCP with VXLAN Virtual Extensible LAN (VXLAN) extends Layer 2 domains over a Layer 3 data center network. The end devices do not know that their traffic is passing through VXLAN tunnels. Also, the traffic classification based on the DSCP field in the IP header and ECN bits are preserved in VXLAN. Because of these reasons, everything that has b

    2024年03月12日
    浏览(38)
  • Chapter 8 - 18. Congestion Management in TCP Storage Networks

    Comparison with Lossless Networks Recall that in Fibre Channel fabrics (explained in  Chapter 3 , “ Detecting Congestion in Fibre Channel Fabrics ”) and lossless Ethernet networks (explained in  Chapter 7 ), when the source of congestion is within an end-device, these devices are called slow-drain devices and they are detected using the metrics of the

    2024年03月14日
    浏览(48)
  • Chapter 8 - 16. Congestion Management in TCP Storage Networks

    Active Queue Management As previously mentioned, dropping or marking schemes for packets that are waiting in a queue can significantly influence TCP’s behavior on the end devices. These schemes are called Active Queue Management (AQM). 如前所述,针对在队列中等待的数据包的丢弃或标记方案会极大地影响 TCP 在终端设备上的行为

    2024年02月20日
    浏览(37)
  • 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日
    浏览(39)
  • 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)
  • 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)
  • 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)
  • Win11运行出MEMORY_MANAGEMENT蓝屏

    最近蓝屏次数好像挺多的,这些都是蓝屏出来的,这里记录我收集到的解决方案,和我所做的。 2号的时候在事件管理器中发现剪映pro软件有冲突,然后在安全模式下卸载了软件 14号的时候就打开了浏览器,准备刷题,然后又蓝屏了。 然后我找了了以下的方法,尝试了一些,

    2024年02月06日
    浏览(40)
  • 论文笔记-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

领红包