From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Subject: [PATCH] io_uring: rename __io_submit_sqe()
Date: Thu, 21 Nov 2019 21:24:36 +0300 [thread overview]
Message-ID: <228a5ae5d63c61dd4f7349594012bfc7691028a7.1574360634.git.asml.silence@gmail.com> (raw)
__io_submit_sqe() is issuing requests, so call it as
such. Moreover, it ends by calling io_iopoll_req_issued().
Rename it and make terminology clearer.
Signed-off-by: Pavel Begunkov <[email protected]>
---
fs/io_uring.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/io_uring.c b/fs/io_uring.c
index dd220f415c39..fa1cf7263959 100644
--- a/fs/io_uring.c
+++ b/fs/io_uring.c
@@ -2579,8 +2579,8 @@ static int io_req_defer(struct io_kiocb *req)
return -EIOCBQUEUED;
}
-static int __io_submit_sqe(struct io_kiocb *req, struct io_kiocb **nxt,
- bool force_nonblock)
+static int io_issue_sqe(struct io_kiocb *req, struct io_kiocb **nxt,
+ bool force_nonblock)
{
int ret, opcode;
struct sqe_submit *s = &req->submit;
@@ -2685,7 +2685,7 @@ static void io_wq_submit_work(struct io_wq_work **workptr)
s->has_user = (work->flags & IO_WQ_WORK_HAS_MM) != 0;
s->in_async = true;
do {
- ret = __io_submit_sqe(req, &nxt, false);
+ ret = io_issue_sqe(req, &nxt, false);
/*
* We can get EAGAIN for polled IO even though we're
* forcing a sync submission from here, since we can't
@@ -2896,7 +2896,7 @@ static void __io_queue_sqe(struct io_kiocb *req)
struct io_kiocb *nxt = io_prep_linked_timeout(req);
int ret;
- ret = __io_submit_sqe(req, NULL, true);
+ ret = io_issue_sqe(req, NULL, true);
/*
* We async punt it if the file wasn't marked NOWAIT, or if the file
--
2.24.0
next reply other threads:[~2019-11-21 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 18:24 Pavel Begunkov [this message]
2019-11-21 20:08 ` [PATCH] io_uring: rename __io_submit_sqe() Jens Axboe
2019-11-21 20:30 ` Pavel Begunkov
2019-11-21 20:34 ` Jens Axboe
2019-11-22 6:11 ` Bob Liu
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 \
--in-reply-to=228a5ae5d63c61dd4f7349594012bfc7691028a7.1574360634.git.asml.silence@gmail.com \
[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