| .\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk> |
| .\" |
| .\" SPDX-License-Identifier: LGPL-2.0-or-later |
| .\" |
| .TH io_uring_prep_send 3 "March 12, 2022" "liburing-2.2" "liburing Manual" |
| .SH NAME |
| io_uring_prep_send \- prepare a send request |
| .SH SYNOPSIS |
| .nf |
| .B #include <liburing.h> |
| .PP |
| .BI "void io_uring_prep_send(struct io_uring_sqe *" sqe "," |
| .BI " int " sockfd "," |
| .BI " const void *" buf "," |
| .BI " size_t " len "," |
| .BI " int " flags ");" |
| .PP |
| .BI "void io_uring_prep_sendto(struct io_uring_sqe *" sqe "," |
| .BI " int " sockfd "," |
| .BI " const void *" buf "," |
| .BI " size_t " len "," |
| .BI " int " flags "," |
| .BI " const struct sockaddr *" addr "," |
| .BI " socklen_t " addrlen ");" |
| .PP |
| .BI "void io_uring_prep_send_bundle(struct io_uring_sqe *" sqe "," |
| .BI " int " sockfd "," |
| .BI " size_t " len "," |
| .BI " int " flags ");" |
| .fi |
| .SH DESCRIPTION |
| .PP |
| The |
| .BR io_uring_prep_send (3) |
| function prepares a send request. The submission queue entry |
| .I sqe |
| is setup to use the file descriptor |
| .I sockfd |
| to start sending the data from |
| .I buf |
| of size |
| .I len |
| bytes and with modifier flags |
| .IR flags . |
| |
| Note that using |
| .B IOSQE_IO_LINK |
| with this request type requires the setting of |
| .B MSG_WAITALL |
| in the |
| .IR flags |
| argument, as a short send isn't a considered an error condition without |
| that being set. |
| |
| This function prepares an async |
| .BR send (2) |
| request. See that man page for details. |
| |
| The |
| .BR io_uring_prep_sendto (3) |
| function prepares a sendto request. The submission queue entry |
| .I sqe |
| is setup to use the file descriptor |
| .I sockfd |
| to start sending the data from |
| .I buf |
| of size |
| .I len |
| bytes and with modifier flags |
| .IR flags . |
| The destination address is specified by |
| .I addr |
| and |
| .I addrlen |
| and must be a valid address for the socket type. |
| |
| This function prepares an async |
| .BR sendto (2) |
| request. See that man page for details. |
| |
| Both of the above send variants may be used with provided buffers, where rather |
| than pass a buffer in directly with the request, |
| .B IOSQE_BUFFER_SELECT |
| is set in the SQE |
| .I flags |
| field, and additionally a buffer group ID is set in the SQE |
| .I buf_group |
| field. By using provided buffers with send requests, the application can |
| prevent any kind of reordering of the outgoing data which can otherwise |
| occur if the application has more than one send request inflight for a single |
| socket. This provides better pipelining of data, where previously the app |
| needed to manually serialize sends. |
| |
| The bundle version allows the application to issue a single send request, |
| with a buffer group ID given in the SQE |
| .I buf_group |
| field, which keeps sending from that buffer group until it runs out of buffers. |
| As with any other request using provided buffers, |
| .B IOSQE_BUFFER_SELECT |
| must also be set in the SQE |
| .I flags |
| before submission. Currently |
| .I len |
| must be given as |
| .B 0 |
| otherwise the request will be errored with |
| .B -EINVAL |
| as the result code. Future versions may allow setting |
| .I |
| to limit the transfer size. A single CQE is posted for the send, with the result |
| being how many bytes were sent, on success. When used with provided buffers, |
| send or send bundle will contain the starting buffer group ID in the CQE |
| .I flags |
| field. The number of bytes sent starts from there, and will be in contiguous |
| buffer IDs after that. Send bundle, and send with provided buffers in general, |
| are available since kernel 6.10, and can be further identified by checking for |
| the |
| .B IORING_FEAT_SEND_BUF_SELECT |
| flag returned in when using |
| .BR io_uring_init_queue_params (3) |
| to setup the ring. |
| |
| .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. |
| .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 send (2) |
| .BR sendto (2) |