From: Mateusz Guzik <mjguzik@gmail.com>
To: yuzhao@google.com
Cc: akpm@linux-foundation.org, willy@infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Mateusz Guzik <mjguzik@gmail.com>
Subject: [PATCH] mm: remove an avoidable load of page refcount in page_ref_add_unless
Date: Sat, 7 Dec 2024 09:29:31 +0100 [thread overview]
Message-ID: <20241207082931.1707465-1-mjguzik@gmail.com> (raw)
Explicitly pre-checking the count adds nothing as atomic_add_unless
starts with doing the same thing. iow no functional changes.
disasm of stock filemap_get_read_batch from perf top while running
readseek2_processes -t 24:
0.04 │ cb: mov 0x34(%rbx),%eax # first load
73.11 │ test %eax,%eax
│ ↓ je 1bd
0.09 │ mov 0x34(%rbx),%eax # second load
1.01 │ d9: test %eax,%eax
│ ↓ je 1bd
0.06 │ lea 0x1(%rax),%edx
0.00 │ lea 0x34(%rbx),%r14
0.00 │ lock cmpxchg %edx,0x34(%rbx)
14.06 │ ↑ jne d9
Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
---
I did not bother benchmarking, I don't think there is anything
warranting it for this one. fwiw it plausibly is worth few % in a
microbenchmark at higher core count.
include/linux/page_ref.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/page_ref.h b/include/linux/page_ref.h
index 8c236c651d1d..fa203894876f 100644
--- a/include/linux/page_ref.h
+++ b/include/linux/page_ref.h
@@ -234,7 +234,7 @@ static inline bool page_ref_add_unless(struct page *page, int nr, int u)
rcu_read_lock();
/* avoid writing to the vmemmap area being remapped */
- if (!page_is_fake_head(page) && page_ref_count(page) != u)
+ if (!page_is_fake_head(page))
ret = atomic_add_unless(&page->_refcount, nr, u);
rcu_read_unlock();
--
2.43.0
next reply other threads:[~2024-12-07 8:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-07 8:29 Mateusz Guzik [this message]
2024-12-09 9:28 ` David Hildenbrand
2024-12-09 10:25 ` Mateusz Guzik
2024-12-09 10:56 ` David Hildenbrand
2024-12-09 12:33 ` Mateusz Guzik
2024-12-09 14:22 ` David Hildenbrand
2024-12-09 14:30 ` Mateusz Guzik
2024-12-09 14:46 ` David Hildenbrand
2025-01-07 4:41 ` Yu Zhao
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=20241207082931.1707465-1-mjguzik@gmail.com \
--to=mjguzik@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.org \
--cc=yuzhao@google.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