diff options
| author |   Uday Shankar <ushankar@purestorage.com> | 2025-05-29 17:47:11 -0600 |
|---|---|---|
| committer |   Jens Axboe <axboe@kernel.dk> | 2025-05-31 14:38:26 -0600 |
| commit | bf098d72696db1a947e72d549ec861dc1092deef (patch) | |
| tree | 109704ad95d514a97db24dbf1ee068b7c9bbc7f7 /scripts/lib/kdoc/kdoc_files.py | |
| parent | ublk: have a per-io daemon instead of a per-queue daemon (diff) | |
| download | linux-rng-bf098d72696db1a947e72d549ec861dc1092deef.tar.xz linux-rng-bf098d72696db1a947e72d549ec861dc1092deef.zip | |
selftests: ublk: kublk: plumb q_id in io_uring user_data
Currently, when we process CQEs, we know which ublk_queue we are working
on because we know which ring we are working on, and ublk_queues and
rings are in 1:1 correspondence. However, as we decouple ublk_queues
from ublk server threads, ublk_queues and rings will no longer be in 1:1
correspondence - each ublk server thread will have a ring, and each
thread may issue commands against more than one ublk_queue. So in order
to know which ublk_queue a CQE refers to, plumb that information in the
associated SQE's user_data.
Signed-off-by: Uday Shankar <ushankar@purestorage.com>
Reviewed-by: Ming Lei <ming.lei@redhat.com>
Link: https://lore.kernel.org/r/20250529-ublk_task_per_io-v8-2-e9d3b119336a@purestorage.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_files.py')
0 files changed, 0 insertions, 0 deletions