From: "tip-bot2 for Andrzej Hajda" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Andrzej Hajda <andrzej.hajda@intel.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Andi Shyti <andi.shyti@linux.intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: locking/core] io_uring: use __xchg if possible
Date: Sun, 12 Mar 2023 14:41:13 -0000 [thread overview]
Message-ID: <167863207362.5837.13623012047790271971.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20230118154450.73842-5-andrzej.hajda@intel.com>
The following commit has been merged into the locking/core branch of tip:
Commit-ID: bd1e2670ebd10ad727b92ddd424cca270314f5ee
Gitweb: https://git.kernel.org/tip/bd1e2670ebd10ad727b92ddd424cca270314f5ee
Author: Andrzej Hajda <andrzej.hajda@intel.com>
AuthorDate: Wed, 18 Jan 2023 16:44:48 +01:00
Committer: Peter Zijlstra <peterz@infradead.org>
CommitterDate: Sat, 11 Mar 2023 14:03:59 +01:00
io_uring: use __xchg if possible
Recently introduced helper simplifies the code.
Signed-off-by: Andrzej Hajda <andrzej.hajda@intel.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Link: https://lore.kernel.org/r/20230118154450.73842-5-andrzej.hajda@intel.com
---
io_uring/io_uring.c | 7 ++-----
io_uring/slist.h | 6 ++----
2 files changed, 4 insertions(+), 9 deletions(-)
diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c
index fd1cc35..0cd89a3 100644
--- a/io_uring/io_uring.c
+++ b/io_uring/io_uring.c
@@ -54,6 +54,7 @@
#include <linux/fdtable.h>
#include <linux/mm.h>
#include <linux/mman.h>
+#include <linux/non-atomic/xchg.h>
#include <linux/percpu.h>
#include <linux/slab.h>
#include <linux/bvec.h>
@@ -1131,8 +1132,6 @@ static void __io_req_find_next_prep(struct io_kiocb *req)
static inline struct io_kiocb *io_req_find_next(struct io_kiocb *req)
{
- struct io_kiocb *nxt;
-
/*
* If LINK is set, we have dependent requests in this chain. If we
* didn't fail this request, queue the first one up, moving any other
@@ -1141,9 +1140,7 @@ static inline struct io_kiocb *io_req_find_next(struct io_kiocb *req)
*/
if (unlikely(req->flags & IO_DISARM_MASK))
__io_req_find_next_prep(req);
- nxt = req->link;
- req->link = NULL;
- return nxt;
+ return __xchg(&req->link, NULL);
}
static void ctx_flush_and_put(struct io_ring_ctx *ctx, bool *locked)
diff --git a/io_uring/slist.h b/io_uring/slist.h
index 7c198a4..051e577 100644
--- a/io_uring/slist.h
+++ b/io_uring/slist.h
@@ -2,6 +2,7 @@
#define INTERNAL_IO_SLIST_H
#include <linux/io_uring_types.h>
+#include <linux/non-atomic/xchg.h>
#define wq_list_for_each(pos, prv, head) \
for (pos = (head)->first, prv = NULL; pos; prv = pos, pos = (pos)->next)
@@ -99,10 +100,7 @@ static inline void wq_list_del(struct io_wq_work_list *list,
static inline
struct io_wq_work_node *wq_stack_extract(struct io_wq_work_node *stack)
{
- struct io_wq_work_node *node = stack->next;
-
- stack->next = node->next;
- return node;
+ return __xchg(&stack->next, stack->next->next);
}
static inline struct io_wq_work *wq_next_work(struct io_wq_work *work)
next prev parent reply other threads:[~2023-03-12 14:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 15:35 [PATCH v5 0/7] Introduce __xchg, non-atomic xchg Andrzej Hajda
2023-01-18 15:44 ` [PATCH v5 1/7] arch: rename all internal names __xchg to __arch_xchg Andrzej Hajda
2023-01-18 15:44 ` [PATCH v5 2/7] linux/include: add non-atomic version of xchg Andrzej Hajda
2023-02-27 9:53 ` [Intel-gfx] " Andi Shyti
2023-03-12 14:41 ` [tip: locking/core] " tip-bot2 for Andrzej Hajda
2023-01-18 15:44 ` [PATCH v5 3/7] arch/*/uprobes: simplify arch_uretprobe_hijack_return_addr Andrzej Hajda
2023-02-27 9:54 ` [Intel-gfx] " Andi Shyti
2023-03-12 14:41 ` [tip: locking/core] " tip-bot2 for Andrzej Hajda
2023-01-18 15:44 ` [PATCH v5 4/7] llist: simplify __llist_del_all Andrzej Hajda
2023-02-27 9:55 ` [Intel-gfx] " Andi Shyti
2023-03-12 14:41 ` [tip: locking/core] " tip-bot2 for Andrzej Hajda
2023-01-18 15:44 ` [PATCH v5 5/7] io_uring: use __xchg if possible Andrzej Hajda
2023-02-27 9:59 ` [Intel-gfx] " Andi Shyti
2023-03-12 14:41 ` tip-bot2 for Andrzej Hajda [this message]
2023-01-18 15:44 ` [PATCH v5 6/7] qed: " Andrzej Hajda
2023-02-27 9:56 ` [Intel-gfx] " Andi Shyti
2023-03-12 14:41 ` [tip: locking/core] " tip-bot2 for Andrzej Hajda
2023-01-18 15:44 ` [PATCH v5 7/7] drm/i915/gt: use __xchg instead of internal helper Andrzej Hajda
2023-02-27 9:58 ` [Intel-gfx] " Andi Shyti
2023-03-12 14:41 ` [tip: locking/core] " tip-bot2 for Andrzej Hajda
2023-03-14 9:58 ` tip-bot2 for Andrzej Hajda
2023-02-27 9:53 ` [Intel-gfx] [PATCH v5 1/7] arch: rename all internal names __xchg to __arch_xchg Andi Shyti
2023-03-12 14:41 ` [tip: locking/core] " tip-bot2 for Andrzej Hajda
2023-04-29 7:03 ` [tip: locking/core] locking/arch: Rename all internal __xchg() names to __arch_xchg() tip-bot2 for Andrzej Hajda
2023-04-29 7:18 ` tip-bot2 for Andrzej Hajda
2023-02-22 10:36 ` [Intel-gfx] [PATCH v5 0/7] Introduce __xchg, non-atomic xchg Andrzej Hajda
2023-02-22 17:04 ` Peter Zijlstra
2023-02-23 21:24 ` [Intel-gfx] " Andrzej Hajda
2023-02-27 13:49 ` Peter Zijlstra
2024-04-05 14:47 ` Jani Nikula
2024-04-05 16:20 ` Andrzej Hajda
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=167863207362.5837.13623012047790271971.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=andi.shyti@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®