.\" Copyright (C) 2022 Stefan Roesch <email@example.com>
.\" SPDX-License-Identifier: LGPL-2.0-or-later
.TH io_uring_sqe_set_flags "January 25, 2022" "liburing-2.1" "liburing Manual"
io_uring_sqe_set_flags - set flags for submission queue entry
.BR "#include <liburing.h>"
.BI "void io_uring_sqe_set_flags(struct io_uring_sqe *sqe,"
.BI " unsigned flags)"
The io_uring_sqe_set_flags() function allows the caller to change the
behavior of the submission queue entry by specifying flags. It enables the
belonging to the
submission queue entry param.
is a bit mask of 0 or more of the following values ORed together:
Use registered files that previously registered buffers.
Normal operation for io_uring is to try and issue an sqe as non-blocking first,
and if that fails, execute it in an async manner. To support more efficient
overlapped operation of requests that the application knows/assumes will
always (or most of the time) block, the application can ask for an sqe to be
issued async from the start.
When this flag is specified, the SQE forms a link with the next SQE in the
submission ring. That next SQE will not be started before the previous request
completes. This, in effect, forms a chain of SQEs, which can be arbitrarily
long. The tail of the chain is denoted by the first SQE that does not have this
flag set. Chains are not supported across submission boundaries. EVen if the
last SQE in a submission has this flag set, it will still terminate the current
chain. This flag has no effect on previous SQE submissions, nor does it impact
SQEs that are outside of the chain tail. This means that multiple chains can be
executing in parallel, or chains and individual SQEs. Only members inside the
chain are serialized. A chain of SQEs will be broken, if any request in that
chain ends in error.
When this flag is specified, the SQE will not be started before previously
submitted SQEs have completed, and new SQEs will not be started before this
.SH RETURN VALUE
.SH SEE ALSO
.BR io_uring_submit (3), io_uring_register(3)