1fi_tcp(7) Libfabric v1.12.1 fi_tcp(7)
2
3
4
6 fi_tcp - The msg sockets Fabric Provider
7
9 The tcp provider can be used on any system that supports TCP sockets.
10 The provider is not intended to provide performance improvements over
11 regular TCP sockets, but rather to allow developers to write, test,and
12 debug application code even on platforms that do not have high-perfor‐
13 mance fabric hardware.
14
16 The following features are supported
17
18 Endpoint types
19 FI_EP_MSG is the only supported endpoint type. Reliable data‐
20 gram endpoint over TCP sockets can be achieved by layering RxM
21 over tcp provider.
22 FI_EP_RDM is supported by layering ofi_rxm provider on top of the tcp
23 provider.
24
25 Endpoint capabilities
26 The tcp provider currently supports FI_MSG, FI_RMA
27
28 Progress
29 Currently tcp provider supports only FI_PROGRESS_MANUAL
30
31 Shared Rx Context
32 The tcp provider supports shared receive context
33
34 Multi recv buffers
35 The tcp provider supports multi recv buffers
36
38 The tcp provider check for the following enviroment variables -
39
40 FI_TCP_IFACE
41 A specific can be requested with this variable
42
43 FI_TCP_PORT_LOW_RANGE/FI_TCP_PORT_HIGH_RANGE
44 These variables are used to set the range of ports to be used by
45 the tcp provider for its passive endpoint creation. This is
46 useful where only a range of ports are allowed by firewall for
47 tcp connections.
48
50 The tcp provider is implemented over TCP sockets to emulate libfabric
51 API. Hence the performance may be lower than what an application might
52 see implementing to sockets directly, depending on the types of data
53 transfers the application is trying to achieve.
54
56 fabric(7), fi_provider(7), fi_getinfo(3)
57
59 OpenFabrics.
60
61
62
63Libfabric Programmer's Manual 2020-04-14 fi_tcp(7)