From: "André Almeida" <andrealmeid@igalia.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Darren Hart <dvhart@infradead.org>,
Davidlohr Bueso <dave@stgolabs.net>
Subject: Re: [PATCH] futex: Improve get_inode_sequence_number()
Date: Thu, 3 Oct 2024 10:28:57 -0300 [thread overview]
Message-ID: <390874e9-eddd-494d-9bc0-62b34a9bb29b@igalia.com> (raw)
In-Reply-To: <20241003121921.922394-1-ubizjak@gmail.com>
Hi Uros,
Em 03/10/2024 09:18, Uros Bizjak escreveu:
> Rewrite FOR loop to a DO-WHILE loop where returns are moved out of
> the loop. Use atomic64_inc_return() instead of atomic64_add_return().
>
> Use !atomic64_try_cmpxchg_relaxed(*ptr, &old, new) instead of
> atomic64_cmpxchg_relaxed (*ptr, old, new) != old. x86 CMPXCHG
> instruction returns success in ZF flag, so this change saves
> a compare after CMPXCHG..
>
> Note that due to early return, "old" equals to 0 before
> atomic64_cmpxchg_relaxed(), so initialization of variable to 0
> is not needed.
>
Despite the implicitly `old = 0`, I think it makes people life easier to
know explicitly that `old = 0` in the cmpxchg() call.
Also, please state in the commit message the motivation of doing this
change. Is to make the code simpler or to try to save some instructions?
The compiler might be already saving such instructions for us :)
> Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@kernel.org>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Darren Hart <dvhart@infradead.org>
> Cc: Davidlohr Bueso <dave@stgolabs.net>
> Cc: "André Almeida" <andrealmeid@igalia.com>
> ---
> kernel/futex/core.c | 17 +++++++----------
> 1 file changed, 7 insertions(+), 10 deletions(-)
>
> diff --git a/kernel/futex/core.c b/kernel/futex/core.c
> index 136768ae2637..665501c885d0 100644
> --- a/kernel/futex/core.c
> +++ b/kernel/futex/core.c
> @@ -173,23 +173,20 @@ futex_setup_timer(ktime_t *time, struct hrtimer_sleeper *timeout,
> static u64 get_inode_sequence_number(struct inode *inode)
> {
> static atomic64_t i_seq;
> - u64 old;
> + u64 old, new;
>
> /* Does the inode already have a sequence number? */
> old = atomic64_read(&inode->i_sequence);
> if (likely(old))
> return old;
>
> - for (;;) {
> - u64 new = atomic64_add_return(1, &i_seq);
> - if (WARN_ON_ONCE(!new))
> - continue;
> + do {
> + new = atomic64_inc_return(&i_seq);
> + } while (WARN_ON_ONCE(!new));
>
> - old = atomic64_cmpxchg_relaxed(&inode->i_sequence, 0, new);
> - if (old)
> - return old;
> - return new;
> - }
> + if (!atomic64_try_cmpxchg_relaxed(&inode->i_sequence, &old, new))
> + return old;
> + return new;
> }
>
> /**
next prev parent reply other threads:[~2024-10-03 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 12:18 Uros Bizjak
2024-10-03 13:28 ` André Almeida [this message]
2024-10-03 13:44 ` Uros Bizjak
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=390874e9-eddd-494d-9bc0-62b34a9bb29b@igalia.com \
--to=andrealmeid@igalia.com \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=ubizjak@gmail.com \
/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®