Proceedings of the 2018 Conference of the ACM Special Interest Group on Data Communication 2018
DOI: 10.1145/3230543.3230557
|View full text |Cite
|
Sign up to set email alerts
|

Revisiting network support for RDMA

Abstract: The advent of RoCE (RDMA over Converged Ethernet) has led to a significant increase in the use of RDMA in datacenter networks. To achieve good performance, RoCE requires a lossless network which is in turn achieved by enabling Priority Flow Control (PFC) within the network. However, PFC brings with it a host of problems such as head-of-the-line blocking, congestion spreading, and occasional deadlocks. Rather than seek to fix these issues, we instead ask: is PFC fundamentally required to support RDMA over Ether… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
47
0

Year Published

2018
2018
2023
2023

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 154 publications
(48 citation statements)
references
References 25 publications
1
47
0
Order By: Relevance
“…By contrast, because it operates only over a single hop, BFC's control loop is shorter and simpler to configure, and can therefore support higher utilization for a given target tail latency. Selective retransmission: We can remove the need for all-or-nothing PFC pause frames for RDMA by changing the standard to support selective retransmission in hardware, as suggested by IRN [27]. Handling arbitrary out-of-order packets is non-trivial in hardware, however, and flows can still experience deep packet buffers and packet loss, especially during incast events.…”
Section: Related Workmentioning
confidence: 99%
“…By contrast, because it operates only over a single hop, BFC's control loop is shorter and simpler to configure, and can therefore support higher utilization for a given target tail latency. Selective retransmission: We can remove the need for all-or-nothing PFC pause frames for RDMA by changing the standard to support selective retransmission in hardware, as suggested by IRN [27]. Handling arbitrary out-of-order packets is non-trivial in hardware, however, and flows can still experience deep packet buffers and packet loss, especially during incast events.…”
Section: Related Workmentioning
confidence: 99%
“…PFC can achieve a lossless network when configured correctly. PFC is a coarse-grained mechanism which can lead to some problems as shown in Reference [21]. For example, as shown in Figure 1, when the congestion occurs in the S1 switch and the queue size of the ingress port exceeds the threshold, a PFC PAUSE frame will be sent to the upstream switch (L1) due to the cascading effect of PAUSE frame and switch L1 stops sending data to switch S1.…”
Section: Priority Flow Controlmentioning
confidence: 99%
“…Some other congestion control protocols are also proposed, such as DCQCN [12], TIMELY [25] and IRN [21]. DCQCN is a rate-based, end-to-end congestion control protocol, that builds upon QCN and DCTCP.…”
Section: Other Relevant Protocolmentioning
confidence: 99%
See 1 more Smart Citation
“…Typically, polling is relying on the last packet of a written message to detect request completion. However, the correctness of this polling-based approach depends on the delivery of the message in order to avoid anticipated last packet delivery or memory overwritten by an older message [18].…”
Section: Communication Paradigmsmentioning
confidence: 99%