File: fi_control.3.md

package info (click to toggle)
mpich 4.3.0%2Breally4.2.1-1
  • links: PTS, VCS
  • area: main
  • in suites: sid, trixie
  • size: 419,120 kB
  • sloc: ansic: 1,215,557; cpp: 74,755; javascript: 40,763; f90: 20,649; sh: 18,463; xml: 14,418; python: 14,397; perl: 13,772; makefile: 9,279; fortran: 8,063; java: 4,553; asm: 324; ruby: 176; lisp: 19; php: 8; sed: 4
file content (59 lines) | stat: -rw-r--r-- 1,708 bytes parent folder | download | duplicates (4)
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
---
layout: page
title: fi_control(3)
tagline: Libfabric Programmer's Manual
---
{% include JB/setup %}

# NAME

fi_control \- Perform an operation on a fabric resource.

# SYNOPSIS

```c
#include <rdma/fabric.h>

int fi_control(struct fid *fid, int command, void *arg);
int fi_alias(struct fid *fid, struct fid **alias_fid, uint64_t flags);
int fi_get_val(struct fid *fid, int name, void *val);
int fi_set_val(struct fid *fid, int name, void *val);
```


# ARGUMENTS

*fid*
: Fabric resource

*command*
: Operation to perform

*arg*
: Optional argument to the command

# DESCRIPTION

The fi_control operation is used to perform one or more operations on a
fabric resource.  Conceptually, fi_control is similar to the POSIX fcntl
routine.  The exact behavior of using fi_control depends on the fabric
resource being operated on, the specified command, and any provided
arguments for the command.  For specific details, see the fabric resource
specific help pages noted below.

fi_alias, fi_get_val, and fi_set_val are wrappers for fi_control with
commands FI_ALIAS, FI_GET_VAL, FI_SET_VAL, respectively. fi_alias creates
an alias of the specified fabric resource. fi_get_val reads the value of
the named parameter associated with the fabric resource, while fi_set_val
updates that value. Available parameter names depend on the type of the
fabric resource and the provider in use. Providers may define provider
specific names in the provider extension header files ('rdma/fi_ext_*.h').
Please refer to the provider man pages for details. 

# SEE ALSO

[`fi_endpoint`(3)](fi_endpoint.3.html),
[`fi_cm`(3)](fi_cm.3.html),
[`fi_cntr`(3)](fi_cntr.3.html),
[`fi_cq`(3)](fi_cq.3.html),
[`fi_eq`(3)](fi_eq.3.html),