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
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
|
.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
.\"
.\" SPDX-License-Identifier: LGPL-2.0-or-later
.\"
.TH io_uring_prep_sendmsg 3 "March 12, 2022" "liburing-2.2" "liburing Manual"
.SH NAME
io_uring_prep_sendmsg \- prepare a sendmsg request
.SH SYNOPSIS
.nf
.B #include <sys/types.h>
.B #include <sys/socket.h>
.B #include <liburing.h>
.PP
.BI "void io_uring_prep_sendmsg(struct io_uring_sqe *" sqe ","
.BI " int " fd ","
.BI " const struct msghdr *" msg ","
.BI " unsigned " flags ");"
.PP
.BI "void io_uring_prep_sendmsg_zc(struct io_uring_sqe *" sqe ","
.BI " int " fd ","
.BI " const struct msghdr *" msg ","
.BI " unsigned " flags ");"
.fi
.SH DESCRIPTION
.PP
The
.BR io_uring_prep_sendmsg (3)
function prepares a sendmsg request. The submission queue entry
.I sqe
is setup to use the file descriptor
.I fd
to start sending the data indicated by
.I msg
with the
.BR sendmsg (2)
defined flags in the
.I flags
argument.
The
.BR io_uring_prep_sendmsg_zc (3)
accepts the same parameters as
.BR io_uring_prep_sendmsg (3)
but prepares a zerocopy sendmsg request.
See
.BR io_uring_prep_send (3)
for a description of flags that can be set in the SQE
.I ioprio
field. In addition to those, the zero-copy send also supports setting
.B IORING_SEND_ZC_REPORT_USAGE .
If set, the notification CQE
.I res
field will report the number of bytes that were copied rather than sent with
zero copy. A value of
.B 0
indicates success. If the value is
.B IORING_NOTIF_USAGE_ZC_COPIED ,
then data was copied.
As opposed to non-zerocopy send requests, a zerocopy send will usually
generate two CQEs. The first CQE holds the result of the send operation itself,
and if that CQE has
.B IORING_CQE_F_MORE
set in the CQE
.I flags
field, then a second notification CQE will be posted for the operation. This
second notification tells the application that the memory associated with the
send is safe to get reused. The second CQE will have
.B IORING_CQE_F_NOTIF
set in the CQE
.I flags
field. Also see the
.BR io_uring_enter (2)
man page for a fuller description of the notification CQE.
Note that using
.B IOSQE_IO_LINK
with this request type requires the setting of
.B MSG_WAITALL
in the
.I flags
argument, as a short send isn't considered an error condition without
that being set.
This function prepares an async
.BR sendmsg (2)
request. See that man page for details.
.SH RETURN VALUE
None
.SH ERRORS
The CQE
.I res
field will contain the result of the operation. See the related man page for
details on possible values. Note that where synchronous system calls will return
.B -1
on failure and set
.I errno
to the actual error value, io_uring never uses
.IR errno .
Instead it returns the negated
.I errno
directly in the CQE
.I res
field. Some common error cases are:
.TP
.B -ENOMEM
The
.BR ulimit (1)
-l setting is too low to support the size of the attempted zero copy send.
Increasing the limit may help
.TP
.B -ENOMEM
The kernel ran out of memory.
.P
.SH NOTES
As with any request that passes in data in a struct, that data must remain
valid until the request has been successfully submitted. It need not remain
valid until completion. Once a request has been submitted, the in-kernel
state is stable. Very early kernels (5.4 and earlier) required state to be
stable until the completion occurred. Applications can test for this
behavior by inspecting the
.B IORING_FEAT_SUBMIT_STABLE
flag passed back from
.BR io_uring_queue_init_params (3).
.SH SEE ALSO
.BR io_uring_get_sqe (3),
.BR io_uring_submit (3),
.BR io_uring_buf_ring_init (3),
.BR io_uring_buf_ring_add (3),
.BR sendmsg (2)
|
