From: Pavel Begunkov <[email protected]>
To: Hao Xu <[email protected]>, [email protected]
Cc: Jens Axboe <[email protected]>
Subject: Re: [PATCH v3] io_uring: switch cancel_hash to use per entry spinlock
Date: Wed, 8 Jun 2022 12:27:53 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 6/8/22 12:12, Hao Xu wrote:
> From: Hao Xu <[email protected]>
>
> Add a new io_hash_bucket structure so that each bucket in cancel_hash
> has separate spinlock. Use per entry lock for cancel_hash, this removes
> some completion lock invocation and remove contension between different
> cancel_hash entries.
Thanks for making the changes, the big picture looks good,
I'll review in a day or two
> Signed-off-by: Hao Xu <[email protected]>
> ---
>
> v1->v2:
> - Add per entry lock for poll/apoll task work code which was missed
> in v1
> - add an member in io_kiocb to track req's indice in cancel_hash
>
> v2->v3:
> - make struct io_hash_bucket align with cacheline to avoid cacheline
> false sharing.
> - re-calculate hash value when deleting an entry from cancel_hash.
> (cannot leverage struct io_poll to store the indice since it's
> already 64 Bytes)
>
> io_uring/cancel.c | 14 +++++++--
> io_uring/cancel.h | 6 ++++
> io_uring/fdinfo.c | 9 ++++--
> io_uring/io_uring.c | 8 +++--
> io_uring/io_uring_types.h | 2 +-
> io_uring/poll.c | 64 +++++++++++++++++++++------------------
> 6 files changed, 65 insertions(+), 38 deletions(-)
--
Pavel Begunkov
next prev parent reply other threads:[~2022-06-08 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 11:12 [PATCH v3] io_uring: switch cancel_hash to use per entry spinlock Hao Xu
2022-06-08 11:27 ` Pavel Begunkov [this message]
2022-06-10 10:21 ` Pavel Begunkov
2022-06-10 15:45 ` Hao Xu
2022-06-11 4:34 ` 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