From: Bijan Mottahedeh <[email protected]>
To: [email protected], [email protected], [email protected]
Subject: [PATCH v4 07/13] io_uring: add rsrc_ref locking routines
Date: Wed, 6 Jan 2021 12:39:16 -0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Encapsulate resource reference locking into separate routines.
Signed-off-by: Bijan Mottahedeh <[email protected]>
---
fs/io_uring.c | 22 ++++++++++++++++------
1 file changed, 16 insertions(+), 6 deletions(-)
diff --git a/fs/io_uring.c b/fs/io_uring.c
index 1d04e82..61e87c4 100644
--- a/fs/io_uring.c
+++ b/fs/io_uring.c
@@ -7265,14 +7265,24 @@ static void io_rsrc_ref_kill(struct percpu_ref *ref)
complete(&data->done);
}
+static inline void io_rsrc_ref_lock(struct io_ring_ctx *ctx)
+{
+ spin_lock_bh(&ctx->rsrc_ref_lock);
+}
+
+static inline void io_rsrc_ref_unlock(struct io_ring_ctx *ctx)
+{
+ spin_unlock_bh(&ctx->rsrc_ref_lock);
+}
+
static void io_sqe_rsrc_set_node(struct io_ring_ctx *ctx,
struct fixed_rsrc_data *rsrc_data,
struct fixed_rsrc_ref_node *ref_node)
{
- spin_lock_bh(&ctx->rsrc_ref_lock);
+ io_rsrc_ref_lock(ctx);
rsrc_data->node = ref_node;
list_add_tail(&ref_node->node, &ctx->rsrc_ref_list);
- spin_unlock_bh(&ctx->rsrc_ref_lock);
+ io_rsrc_ref_unlock(ctx);
percpu_ref_get(&rsrc_data->refs);
}
@@ -7289,9 +7299,9 @@ static int io_sqe_files_unregister(struct io_ring_ctx *ctx)
if (!backup_node)
return -ENOMEM;
- spin_lock_bh(&ctx->rsrc_ref_lock);
+ io_rsrc_ref_lock(ctx);
ref_node = data->node;
- spin_unlock_bh(&ctx->rsrc_ref_lock);
+ io_rsrc_ref_unlock(ctx);
if (ref_node)
percpu_ref_kill(&ref_node->refs);
@@ -7681,7 +7691,7 @@ static void io_rsrc_data_ref_zero(struct percpu_ref *ref)
data = ref_node->rsrc_data;
ctx = data->ctx;
- spin_lock_bh(&ctx->rsrc_ref_lock);
+ io_rsrc_ref_lock(ctx);
ref_node->done = true;
while (!list_empty(&ctx->rsrc_ref_list)) {
@@ -7693,7 +7703,7 @@ static void io_rsrc_data_ref_zero(struct percpu_ref *ref)
list_del(&ref_node->node);
first_add |= llist_add(&ref_node->llist, &ctx->rsrc_put_llist);
}
- spin_unlock_bh(&ctx->rsrc_ref_lock);
+ io_rsrc_ref_unlock(ctx);
if (percpu_ref_is_dying(&data->refs))
delay = 0;
--
1.8.3.1
next prev parent reply other threads:[~2021-01-06 20:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 20:39 [PATCH v4 00/13] io_uring: buffer registration enhancements Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 01/13] io_uring: modularize io_sqe_buffer_register Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 02/13] io_uring: modularize io_sqe_buffers_register Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 03/13] io_uring: rename file related variables to rsrc Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 04/13] io_uring: generalize io_queue_rsrc_removal Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 05/13] io_uring: separate ref_list from fixed_rsrc_data Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 06/13] io_uring: split alloc_fixed_file_ref_node Bijan Mottahedeh
2021-01-06 20:39 ` Bijan Mottahedeh [this message]
2021-01-06 20:39 ` [PATCH v4 08/13] io_uring: implement fixed buffers registration similar to fixed files Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 09/13] io_uring: create common fixed_rsrc_ref_node handling routines Bijan Mottahedeh
2021-01-08 1:57 ` Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 10/13] io_uring: generalize files_update functionlity to rsrc_update Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 11/13] io_uring: support buffer registration updates Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 12/13] io_uring: create common fixed_rsrc_data allocation routines Bijan Mottahedeh
2021-01-06 20:39 ` [PATCH v4 13/13] io_uring: support buffer registration sharing Bijan Mottahedeh
2021-01-07 15:53 ` [PATCH v4 00/13] io_uring: buffer registration enhancements Jens Axboe
2021-01-07 17:03 ` Bijan Mottahedeh
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=1609965562-13569-8-git-send-email-bijan.mottahedeh@oracle.com \
[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