Chapter 8 - 13. Congestion Management in TCP Storage Networks

这篇具有很好参考价值的文章主要介绍了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. 当发送方因以下原因检测到数据包丢失时。

a. Retransmission timeout (RTO) or重传超时 (RTO)

b. Receiving third duplicate ACK (Fast Retransmission). 收到第三个重复 ACK(快速重传)。

2. When the sender receives an ECE-marked TCP packet. 当发送方收到 ECE 标记的 TCP 数据包时。

Both events originate at a network port when its queues fill up. This means that the packet drops or marking scheme on a switch can significantly influence TCP’s behavior on the end devices, and hence, these schemes are important in handling congestion in TCP networks. 这两种事件都源于网络端口的队列填满。这意味着,交换机上的数据包丢弃或标记方案会极大地影响 TCP 在终端设备上的行为,因此,这些方案在处理 TCP 网络拥塞时非常重要。

This section explains various states of queues on a network port. These queues are created in the switch buffers, hence the use of the term—Buffer Management. The queues have their own Active Queue Management mechanism as explained later. 本节介绍网络端口上队列的各种状态。这些队列在交换机缓冲区中创建,因此使用了缓冲区管理(Buffer Management文章来源地址https://www.toymoban.com/news/detail-833789.html

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

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

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

相关文章

  • 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 - 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 - 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)
  • Android 13 WRITE_EXTERNAL_STORAGE , READ_EXTERNAL_STORAGE不弹出的问题

    在Android 13(API 33)之前,加入了如下代码 如果 compileSdk 设置 32 或者以下,那么就没什么问题。当设置33 或者以上,系统就会自动设置无权限。那在 33 及以上的怎么设置呢? 看下面的代码。 在xml中如下设置 动态获取权限的代码如下:

    2024年04月27日
    浏览(63)
  • android开发在android13中存储权限发生变化,READ_EXTERNAL_STORAGE,WRITE_EXTERNAL_STORAGE无法使用

    原来的两个存储权限在android13中已经无法使用 在android13中读取图片需要以下权限: 视频权限: 音频权限: 如果需要访问pdf,word等其他类型文件,请使用以下权限:

    2024年02月01日
    浏览(36)
  • 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)

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

支付宝扫一扫打赏

博客赞助

微信扫一扫打赏

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

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

二维码1

领取红包

二维码2

领红包