From: Uladzislau Rezki <urezki@gmail.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Uladzislau Rezki <urezki@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
Lorenzo Stoakes <lstoakes@gmail.com>,
Dennis Zhou <dennis@kernel.org>, Tejun Heo <tj@kernel.org>,
Christoph Lameter <cl@linux.com>
Subject: Re: [PATCH v2 2/2] mm/vmalloc: Use __this_cpu_try_cmpxchg() in preload_this_cpu_lock()
Date: Tue, 28 May 2024 20:36:00 +0200 [thread overview]
Message-ID: <ZlYkEIDqiot10w1s@pc636> (raw)
In-Reply-To: <20240528144345.5980-2-ubizjak@gmail.com>
On Tue, May 28, 2024 at 04:43:14PM +0200, Uros Bizjak wrote:
> Use __this_cpu_try_cmpxchg() instead of
> __this_cpu_cmpxchg (*ptr, old, new) == old in
> preload_this_cpu_lock(). x86 CMPXCHG instruction returns
> success in ZF flag, so this change saves a compare after cmpxchg.
>
> The generated code improves from:
>
> 4bb6: 48 85 f6 test %rsi,%rsi
> 4bb9: 0f 84 10 fa ff ff je 45cf <...>
> 4bbf: 4c 89 e8 mov %r13,%rax
> 4bc2: 65 48 0f b1 35 00 00 cmpxchg %rsi,%gs:0x0(%rip)
> 4bc9: 00 00
> 4bcb: 48 85 c0 test %rax,%rax
> 4bce: 0f 84 fb f9 ff ff je 45cf <...>
>
> to:
>
> 4bb6: 48 85 f6 test %rsi,%rsi
> 4bb9: 0f 84 10 fa ff ff je 45cf <...>
> 4bbf: 4c 89 e8 mov %r13,%rax
> 4bc2: 65 48 0f b1 35 00 00 cmpxchg %rsi,%gs:0x0(%rip)
> 4bc9: 00 00
> 4bcb: 0f 84 fe f9 ff ff je 45cf <...>
>
> No functional change intended.
>
> Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Uladzislau Rezki <urezki@gmail.com>
> Cc: Christoph Hellwig <hch@infradead.org>
> Cc: Lorenzo Stoakes <lstoakes@gmail.com>
> Cc: Dennis Zhou <dennis@kernel.org>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Christoph Lameter <cl@linux.com>
> ---
> v2: Show generated code improvement in the commit message.
> ---
> mm/vmalloc.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index 5d3aa2dc88a8..4f34d935d648 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -1816,7 +1816,7 @@ static void free_vmap_area(struct vmap_area *va)
> static inline void
> preload_this_cpu_lock(spinlock_t *lock, gfp_t gfp_mask, int node)
> {
> - struct vmap_area *va = NULL;
> + struct vmap_area *va = NULL, *tmp;
>
> /*
> * Preload this CPU with one extra vmap_area object. It is used
> @@ -1832,7 +1832,8 @@ preload_this_cpu_lock(spinlock_t *lock, gfp_t gfp_mask, int node)
>
> spin_lock(lock);
>
> - if (va && __this_cpu_cmpxchg(ne_fit_preload_node, NULL, va))
> + tmp = NULL;
> + if (va && !__this_cpu_try_cmpxchg(ne_fit_preload_node, &tmp, va))
> kmem_cache_free(vmap_area_cachep, va);
> }
>
> --
> 2.42.0
>
Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
Thanks!
--
Uladzislau Rezki
next prev parent reply other threads:[~2024-05-28 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 14:43 [PATCH v2 1/2] percpu: Add __this_cpu_try_cmpxchg() Uros Bizjak
2024-05-28 14:43 ` [PATCH v2 2/2] mm/vmalloc: Use __this_cpu_try_cmpxchg() in preload_this_cpu_lock() Uros Bizjak
2024-05-28 18:36 ` Uladzislau Rezki [this message]
2024-05-28 18:50 ` [PATCH v2 1/2] percpu: Add __this_cpu_try_cmpxchg() Uladzislau Rezki
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=ZlYkEIDqiot10w1s@pc636 \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=dennis@kernel.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.