io_uring_register_files - Man Page

register file descriptors


#include <liburing.h>

int io_uring_register_files(struct io_uring *ring,
                            const int *files,
                            unsigned nr_files);

int io_uring_register_files_sparse(struct io_uring *ring,
                            unsigned nr_files);


The io_uring_register_files(3) function registers nr_files number of file descriptors defined by the array files belonging to the ring for subsequent operations.

The io_uring_register_files_sparse(3) function registers an empty file table of nr_files number of file descriptors. The sparse variant is available in kernels 5.19 and later.

Registering a file table is a prerequisite for using any request that uses direct descriptors.

Registered files have less overhead per operation than normal files. This is due to the kernel grabbing a reference count on a file when an operation begins, and dropping it when it's done. When the process file table is shared, for example if the process has ever created any threads, then this cost goes up even more. Using registered files reduces the overhead of file reference management across requests that operate on a file.

Return Value

On success io_uring_register_files(3) and io_uring_register_files_sparse(3) return 0. On failure they return -errno.

See Also

io_uring_get_sqe(3), io_uring_unregister_files(3)

Referenced By

io_uring_prep_accept(3), io_uring_prep_openat(3), io_uring_prep_openat2(3), io_uring_prep_socket(3), io_uring_register_file_alloc_range(3), io_uring_register_ring_fd(3), io_uring_unregister_files(3), io_uring_unregister_ring_fd(3).

The man page io_uring_register_files_sparse(3) is an alias of io_uring_register_files(3).

November 15, 2021 liburing-2.1 liburing Manual