From: Dave Chinner <david@fromorbit.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
"Darrick J. Wong" <djwong@kernel.org>
Subject: Re: [PATCH] fs/xfs: Use atomic64_try_cmpxchg in xlog_grant_{add,sub}_space
Date: Wed, 10 Aug 2022 09:02:44 +1000 [thread overview]
Message-ID: <20220809230244.GJ3600936@dread.disaster.area> (raw)
In-Reply-To: <20220809220511.GI3600936@dread.disaster.area>
On Wed, Aug 10, 2022 at 08:05:11AM +1000, Dave Chinner wrote:
> On Tue, Aug 09, 2022 at 06:56:15PM +0200, Uros Bizjak wrote:
> > Use `!atomic64_try_cmpxchg(ptr, &old, new)` instead of
> > `atomic64_cmpxchg(ptr, old, new) != old` in xlog_grant_{add,sub}_space.
> > This has two benefits:
> >
> > - The x86 cmpxchg instruction returns success in the ZF flag, so this
> > change saves a compare after cmpxchg, as well as a related move
> > instruction in the front of cmpxchg.
> >
> > - atomic64_try_cmpxchg implicitly assigns the *ptr value to &old when
> > cmpxchg fails, enabling further code simplifications.
>
> Do the two cmpxchg operations have the same memory ordering
> semantics on failure?
>
> > This patch has no functional change.
>
> The patch looks ok, but ....
>
> ... I'm about 2 hours away from posting a patchset that completely
> removes the cmpxchg and the new grant head accounting has
> significantly lower fast path overhead. It also opens the door for
> tracking more than 2GB of log space in the grant heads.
FYI, the original RFC for this was posted a bit over a month ago:
https://lore.kernel.org/linux-xfs/20220708015558.1134330-1-david@fromorbit.com/
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2022-08-09 23:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 16:56 [PATCH] fs/xfs: Use atomic64_try_cmpxchg in xlog_grant_{add,sub}_space Uros Bizjak
2022-08-09 22:05 ` Dave Chinner
2022-08-09 23:02 ` Dave Chinner [this message]
2022-08-10 7:02 ` Uros Bizjak
2022-08-10 22:56 ` Dave Chinner
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=20220809230244.GJ3600936@dread.disaster.area \
--to=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@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