io_uring: let to set a range for file slot allocation

From recently io_uring provides an option to allocate a file index for
operation registering fixed files. However, it's utterly unusable with
mixed approaches when for a part of files the userspace knows better
where to place it, as it may race and users don't have any sane way to
pick a slot and hoping it will not be taken.

Let the userspace to register a range of fixed file slots in which the
auto-allocation happens. The use case is splittting the fixed table in
two parts, where on of them is used for auto-allocation and another for
slot-specified operations.

Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
Link: https://lore.kernel.org/r/66ab0394e436f38437cf7c44676e1920d09687ad.1656154403.git.asml.silence@gmail.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
This commit is contained in:
Pavel Begunkov 2022-06-25 11:55:38 +01:00 committed by Jens Axboe
parent e6130eba8a
commit 6e73dffbb9
6 changed files with 61 additions and 7 deletions

View file

@ -233,6 +233,9 @@ struct io_ring_ctx {
unsigned long check_cq;
unsigned int file_alloc_start;
unsigned int file_alloc_end;
struct {
/*
* We cache a range of free CQEs we can use, once exhausted it