From: Andrew Morton <akpm@linux-foundation.org>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] llist: Use try_cmpxchg in llist_add_batch and llist_del_first
Date: Sun, 14 Aug 2022 18:48:23 -0700 [thread overview]
Message-ID: <20220814184823.c6ca2c396db0d8817e518ef9@linux-foundation.org> (raw)
In-Reply-To: <20220712144917.4497-1-ubizjak@gmail.com>
On Tue, 12 Jul 2022 16:49:17 +0200 Uros Bizjak <ubizjak@gmail.com> wrote:
> Use try_cmpxchg instead of cmpxchg (*ptr, old, new) == old in
> llist_add_batch and llist_del_first. x86 CMPXCHG instruction returns
> success in ZF flag, so this change saves a compare after cmpxchg.
>
> Also, try_cmpxchg implicitly assigns old *ptr value to "old" when
> cmpxchg fails, enabling further code simplifications.
>
> No functional change intended.
Well this is strange. Your innocuous little patch:
> --- a/lib/llist.c
> +++ b/lib/llist.c
> @@ -30,7 +30,7 @@ bool llist_add_batch(struct llist_node *new_first, struct llist_node *new_last,
>
> do {
> new_last->next = first = READ_ONCE(head->first);
> - } while (cmpxchg(&head->first, first, new_first) != first);
> + } while (!try_cmpxchg(&head->first, &first, new_first));
>
> return !first;
> }
> @@ -52,18 +52,14 @@ EXPORT_SYMBOL_GPL(llist_add_batch);
> */
> struct llist_node *llist_del_first(struct llist_head *head)
> {
> - struct llist_node *entry, *old_entry, *next;
> + struct llist_node *entry, *next;
>
> entry = smp_load_acquire(&head->first);
> - for (;;) {
> + do {
> if (entry == NULL)
> return NULL;
> - old_entry = entry;
> next = READ_ONCE(entry->next);
> - entry = cmpxchg(&head->first, old_entry, next);
> - if (entry == old_entry)
> - break;
> - }
> + } while (!try_cmpxchg(&head->first, &entry, next));
>
> return entry;
> }
Does this:
x1:/usr/src/25> size lib/llist.o-before lib/llist.o-after
text data bss dec hex filename
541 24 0 565 235 lib/llist.o-before
940 24 0 964 3c4 lib/llist.o-after
with x86_64 allmodconfig, gcc-11.1.0.
No change with allnoconfig, some bloat with defconfig.
I was too lazy to figure out why this happened, but it'd be great if
someone could investigate. Something has gone wrong somewhere.
x1:/usr/src/25> scripts/bloat-o-meter lib/llist.o-before lib/llist.o-after
add/remove: 0/0 grow/shrink: 2/0 up/down: 351/0 (351)
Function old new delta
llist_add_batch 106 286 +180
llist_del_first 106 277 +171
Total: Before=310, After=661, chg +113.23%
in the two functions you touched.
next prev parent reply other threads:[~2022-08-15 1:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 14:49 Uros Bizjak
2022-08-15 1:48 ` Andrew Morton [this message]
2022-08-15 19:20 ` Uros Bizjak
2022-08-15 19:28 ` 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=20220814184823.c6ca2c396db0d8817e518ef9@linux-foundation.org \
--to=akpm@linux-foundation.org \
--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
all inboxes | Powered by JetHome®