From: Hao Xu <[email protected]>
To: [email protected]
Cc: Jens Axboe <[email protected]>, Pavel Begunkov <[email protected]>
Subject: [PATCH 2/3] io_uring: add an io_hash_bucket structure for smaller granularity lock
Date: Mon, 6 Jun 2022 14:57:15 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
From: Hao Xu <[email protected]>
Add a new io_hash_bucket structure so that each bucket in cancel_hash
has separate spinlock. This is a prep patch for later use.
Signed-off-by: Hao Xu <[email protected]>
---
io_uring/cancel.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/io_uring/cancel.h b/io_uring/cancel.h
index 4f35d8696325..b9218310611c 100644
--- a/io_uring/cancel.h
+++ b/io_uring/cancel.h
@@ -4,3 +4,8 @@ int io_async_cancel_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe);
int io_async_cancel(struct io_kiocb *req, unsigned int issue_flags);
int io_try_cancel(struct io_kiocb *req, struct io_cancel_data *cd);
+
+struct io_hash_bucket {
+ spinlock_t lock;
+ struct hlist_head list;
+};
--
2.25.1
next prev parent reply other threads:[~2022-06-06 6:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 6:57 [PATCH v2 0/3] cancel_hash per entry lock Hao Xu
2022-06-06 6:57 ` [PATCH 1/3] io_uring: add hash_index and its logic to track req in cancel_hash Hao Xu
2022-06-06 11:59 ` Pavel Begunkov
2022-06-06 13:47 ` Hao Xu
2022-06-06 6:57 ` Hao Xu [this message]
2022-06-06 11:55 ` [PATCH 2/3] io_uring: add an io_hash_bucket structure for smaller granularity lock Pavel Begunkov
2022-06-06 6:57 ` [PATCH 3/3] io_uring: switch cancel_hash to use per list spinlock Hao Xu
2022-06-06 7:06 ` [PATCH v2 0/3] cancel_hash per entry lock Hao Xu
2022-06-06 12:02 ` Pavel Begunkov
2022-06-06 12:09 ` Pavel Begunkov
2022-06-06 13:39 ` Hao Xu
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] \
/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