From: Alexey Gladkov <legion@kernel.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org, Uros Bizjak <ubizjak@gmail.com>
Subject: Re: [PATCH RESEND 2/2] ucount: Use atomic_long_try_cmpxchg in atomic_long_inc_below
Date: Mon, 31 Oct 2022 20:02:12 +0100 [thread overview]
Message-ID: <Y2AbtAAVBjmya9qJ@example.org> (raw)
In-Reply-To: <20221017144049.3404-3-ubizjak@gmail.com>
On Mon, Oct 17, 2022 at 04:40:49PM +0200, Uros Bizjak wrote:
> Use atomic_long_try_cmpxchg instead of
> atomic_long_cmpxchg (*ptr, old, new) == old in atomic_long_inc_below.
> x86 CMPXCHG instruction returns success in ZF flag, so this change saves
> a compare after cmpxchg (and related move instruction in front of cmpxchg).
>
> Also, atomic_long_try_cmpxchg implicitly assigns old *ptr value to "old"
> when cmpxchg fails, enabling further code simplifications.
>
> No functional change intended.
>
> Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
> Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Reviewed-by: Alexey Gladkov <legion@kernel.org>
Eric, I think the patch looks good. You already reviewed the previous
version [1]. What do you think about this version?
[1] https://lore.kernel.org/lkml/87pmi6z143.fsf@email.froward.int.ebiederm.org/
> ---
> kernel/ucount.c | 14 ++++++--------
> 1 file changed, 6 insertions(+), 8 deletions(-)
>
> diff --git a/kernel/ucount.c b/kernel/ucount.c
> index 74f5b4959feb..2c04589a61ff 100644
> --- a/kernel/ucount.c
> +++ b/kernel/ucount.c
> @@ -214,16 +214,14 @@ void put_ucounts(struct ucounts *ucounts)
>
> static inline bool atomic_long_inc_below(atomic_long_t *v, long u)
> {
> - long c, old;
> - c = atomic_long_read(v);
> - for (;;) {
> + long c = atomic_long_read(v);
> +
> + do {
> if (unlikely(c >= u))
> return false;
> - old = atomic_long_cmpxchg(v, c, c+1);
> - if (likely(old == c))
> - return true;
> - c = old;
> - }
> + } while (!atomic_long_try_cmpxchg(v, &c, c+1));
> +
> + return true;
> }
>
> struct ucounts *inc_ucount(struct user_namespace *ns, kuid_t uid,
> --
> 2.37.3
>
--
Rgrds, legion
prev parent reply other threads:[~2022-10-31 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 14:40 [PATCH RESEND 0/2] ucount: Fix and improve atomic_long_inc_below Uros Bizjak
2022-10-17 14:40 ` [PATCH RESEND 1/2] ucount: Fix atomic_long_inc_below argument type Uros Bizjak
2022-10-17 14:40 ` [PATCH RESEND 2/2] ucount: Use atomic_long_try_cmpxchg in atomic_long_inc_below Uros Bizjak
2022-10-31 19:02 ` Alexey Gladkov [this message]
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=Y2AbtAAVBjmya9qJ@example.org \
--to=legion@kernel.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--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