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
|
.\" Automatically generated by Pandoc 2.9.2.1
.\"
.TH "mlx5dv_get_data_direct_sysfs_path" "3" "" "" ""
.hy
.SH NAME
.PP
mlx5dv_get_data_direct_sysfs_path - Get the sysfs path of a data direct
device
.SH SYNOPSIS
.IP
.nf
\f[C]
#include <infiniband/mlx5dv.h>
int mlx5dv_get_data_direct_sysfs_path(struct ibv_context *context, char *buf,
size_t buf_len)
\f[R]
.fi
.SH DESCRIPTION
.PP
Get the sysfs path of the data direct device that is associated with the
given \f[I]context\f[R].
.PP
This lets an application to discover whether/which data direct device is
associated with the given \f[I]context\f[R].
.SH ARGUMENTS
.TP
\f[I]context\f[R]
RDMA device context to work on.
.TP
\f[I]buf\f[R]
The buffer where to place the sysfs path of the associated data direct
device.
.TP
\f[I]buf_len\f[R]
.IP
.nf
\f[C]
The length of the buffer.
\f[R]
.fi
.SH RETURN VALUE
.PP
Upon success 0 is returned or the value of errno on a failure.
.SH ERRORS
.PP
The below specific error values should be considered.
.TP
ENODEV
.IP
.nf
\f[C]
There is no associated data direct device for the given *context*.
\f[R]
.fi
.TP
ENOSPC
.IP
.nf
\f[C]
The input buffer size is too small to hold the full sysfs path.
\f[R]
.fi
.SH NOTES
.PP
Upon succees, the caller should add the /sys/ prefix to get the full
sysfs path.
.SH SEE ALSO
.PP
\f[I]mlx5dv_reg_dmabuf_mr(3)\f[R]
.SH AUTHOR
.PP
Yishai Hadas <yishaih@nvidia.com>
|
