RE: [PATCH rdma-next 0/3] Support out of order data placement

Hefty, Sean
2017-06-12T20:46:47Z

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 877 bytes --]

> > When transmitter and receiver is enabled to do so, as I described in
> overview section of Documentation, it helps
> > (a) to avoid retransmission - improves network utilization
> > (b) reduces latency due to timers not kicking in.
>
> Yes those benefits are clear. I see no reason why it shouldn't always
> be
> done is my point. Application shouldn't have to care and there is no
> need to make this an additional flag.

The app cares when data from write 2 can be written at the target before data from write 1, especially if the writes target the same memory buffers. (At least I think this is the intent of exposing this to the app.)

Note that the provider can always provide stronger ordering than what the app needs.
N‹§²æìr¸›yúèšØb²X¬¶Ç§vØ^–)Þº{.nÇ+‰·¥Š{±­ÙšŠ{ayº\x1dÊ‡Ú™ë,j\a­¢f£¢·hš‹»öì\x17/oSc¾™Ú³9˜uÀ¦æå‰È&jw¨®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿïêäz¹Þ–Šàþf£¢·hšˆ§~ˆmš