From: Bernd Schubert <[email protected]>
To: "[email protected]" <[email protected]>
Cc: Ming Lei <[email protected]>, Jens Axboe <[email protected]>,
Pavel Begunkov <[email protected]>
Subject: SQPOLL / uring_cmd_iopoll
Date: Fri, 21 Apr 2023 22:09:36 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
Hello,
I was wondering if I could set up SQPOLL for fuse/IORING_OP_URING_CMD
and what would be the latency win. Now I get a bit confused what the
f_op->uring_cmd_iopoll() function is supposed to do.
Is it just there to check if SQEs are can be completed as CQE? In rw.c
io_do_iopoll() it looks like this. I don't follow all code paths in
__io_sq_thread yet, but it looks a like it already checks if the ring
has new entries
to_submit = io_sqring_entries(ctx);
...
ret = io_submit_sqes(ctx, to_submit);
--> it will eventually call into ->uring_cmd() ?
And then io_do_iopoll -> file->f_op->uring_cmd_iopoll is supposed to
check for available cq entries and will submit these? I.e. I just return
1 if when the request is ready? And also ensure that
req->iopoll_completed is set?
I'm also not sure what I should do with struct io_comp_batch * - I don't
have struct request *req_list anywhere in my fuse-uring changes, seems
to be blk-mq specific? So I should just ignore that parameter?
Btw, this might be useful for ublk as well?
Thanks,
Bernd
next reply other threads:[~2023-04-21 22:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 22:09 Bernd Schubert [this message]
2023-04-22 2:13 ` SQPOLL / uring_cmd_iopoll Jens Axboe
2023-04-22 13:40 ` Bernd Schubert
2023-04-24 12:55 ` Bernd Schubert
2023-04-22 12:55 ` Ming Lei
2023-04-22 14:08 ` Jens Axboe
2023-04-23 1:06 ` Ming Lei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox