File: fi_rstream.7.md

package info (click to toggle)
mpich 4.0.2-3
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 423,384 kB
  • sloc: ansic: 1,088,434; cpp: 71,364; javascript: 40,763; f90: 22,829; sh: 17,463; perl: 14,773; xml: 14,418; python: 10,265; makefile: 9,246; fortran: 8,008; java: 4,355; asm: 324; ruby: 176; lisp: 19; php: 8; sed: 4
file content (84 lines) | stat: -rw-r--r-- 2,629 bytes parent folder | download | duplicates (7)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
---
layout: page
title: fi_rstream(7)
tagline: Libfabric Programmer's Manual
---
{% include JB/setup %}

# NAME

fi_rstream

# OVERVIEW

The rstream provider supports stream messaging over
 message based RMA. It maps stream to message over
 a core RMA-based OFI provider. Only Endpoints and EQs
 are needed for connection start-up and messaging. Unlike other
 OFI providers, rstream does not support CQs or memory registration
 of any kind. In order to asynchronously wait for a completion (cm/msg),
 one can use fi_control on the endpoint/eq to get an fd to use in a poll call.
 For messaging completions, use FI_PEEK on send/recv after poll to see what type of
 transaction has transpired.

# SUPPORTED FEATURES

The rstream provider currently supports *FI_MSG* capabilities.

*Endpoint types*
: The provider supports only endpoint type *FI_EP_SOCK_STREAM*.

*Endpoint capabilities* : The following data transfer interface is
supported: *fi_msg*.

*Modes*
: The provider does not require the use of any mode bits but supports
  core providers that require FI_CONTEXT and FI_RX_CQ_DATA.

*Progress*
: The rstream provider only supports *FI_PROGRESS_MANUAL*.

*Threading Model*
: The provider supports FI_THREAD_SAFE

*Verbs-iWarp*
: The provider has added features to enable iWarp. To use this feature, the
  ep protocol iWarp must be requested in an fi_getinfo call.

# LIMITATIONS

The rstream provider is experimental and lacks performance validation and
 extensive testing. The iWarp protocol may need extra initialization work to re-enable.
 Currently the rstream provider is used to by the rsockets-OFI library as a ULP and
 hooks into the core provider verbs. It is not interoperable with the previous rsockets(v1)
 protocol. There are default settings that limit the message stream (provider
 memory region size and CQ size). These can be modified by fi_setopt.

# SETTINGS

The *rstream* provider settings can be modified via fi_setopt on the
 endpoint (FI_OPT_ENDPOINT) along with the following parameters:

*FI_OPT_SEND_BUF_SIZE*
: Size of the send buffer. Default is 32KB.

*FI_OPT_RECV_BUF_SIZE*
: Size of the recv buffer. Default is 32KB.

*FI_OPT_TX_SIZE*
: Size of the send queue. Default is 384.

*FI_OPT_RX_SIZE*
: Size of the recv queue. Default is 384.

# OFI EXTENSIONS

The rstream provider has extended the current OFI API set in order to enable a
 user implementation of Poll. Specifically sendmsg(FI_PEEK) is supported
 which replicates the behavior of the recvmsg(FI_PEEK) feature.

# SEE ALSO

[`fabric`(7)](fabric.7.html),
[`fi_provider`(7)](fi_provider.7.html),
[`fi_getinfo`(3)](fi_getinfo.3.html)