From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Samuel Holland <samuel.holland@sifive.com>
Cc: "Darren Hart" <dvhart@infradead.org>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"André Almeida" <andrealmeid@igalia.com>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org,
"Alexandre Ghiti" <alex@ghiti.fr>,
"H. Peter Anvin" <hpa@zytor.com>,
"Kiryl Shutsemau" <kas@kernel.org>,
"Sean Christopherson" <seanjc@google.com>,
"Charlie Jenkins" <charlie@rivosinc.com>,
"Charles Mirabile" <cmirabil@redhat.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Sven Schnelle" <svens@linux.ibm.com>,
"Thomas Huth" <thuth@redhat.com>,
"Jisheng Zhang" <jszhang@kernel.org>,
"Thomas Gleixner" <tglx@kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Paul Walmsley" <pjw@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Borislav Petkov" <bp@alien8.de>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
x86@kernel.org, "Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>,
"Heiko Carstens" <hca@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Arnd Bergmann" <arnd@arndb.de>
Subject: Re: [RFC PATCH v2 7/7] futex: Use runtime constants for __futex_hash() hot path
Date: Tue, 17 Mar 2026 10:41:07 +0530 [thread overview]
Message-ID: <9fa8ef20-1da2-48e3-a9d8-340a5106cea8@amd.com> (raw)
In-Reply-To: <f25ed5b8-e785-414a-b13e-85c1a787665d@sifive.com>
Hello Samuel,
On 3/17/2026 8:36 AM, Samuel Holland wrote:
>> @@ -1913,7 +1909,7 @@ int futex_hash_allocate_default(void)
>> * 16 <= threads * 4 <= global hash size
>> */
>> buckets = roundup_pow_of_two(4 * threads);
>> - buckets = clamp(buckets, 16, futex_hashmask + 1);
>> + buckets = clamp(buckets, 16, __futex_mask + 1);
>>
>> if (current_buckets >= buckets)
>> return 0;
>> @@ -1983,10 +1979,19 @@ static int __init futex_init(void)
>> hashsize = max(4, hashsize);
>> hashsize = roundup_pow_of_two(hashsize);
>> #endif
>> - futex_hashshift = ilog2(hashsize);
>> + __futex_mask = hashsize - 1;
>> + __futex_shift = ilog2(hashsize);
>
> __futex_mask is always a power of two minus 1, in other words all low bits set.
> Would it be worth using an n-bit zero extension operation instead of an
> arbitrary 32-bit mask? This would use fewer instructions on some architectures:
> for example a single ubfx on arm64 and slli+srli on riscv.
Sure that works for __futex_mask but runtime_const_mask_32() should be
generic enough to handle any mask, no?
Currently, the __futex_hash() with futex_hashmask ends up being:
# ./include/linux/jhash.h:139: __jhash_final(a, b, c);
xor a4,a4,a3 # tmp350, tmp353, tmp334
...
# kernel/futex/core.c:449: return &futex_queues[node][hash & futex_hashmask];
lla a3,.LANCHOR0 # tmp361,
# kernel/futex/core.c:449: return &futex_queues[node][hash & futex_hashmask];
ld a5,0(a3) # __futex_data.hashmask, __futex_data.hashmask
...
# kernel/futex/core.c:449: return &futex_queues[node][hash & futex_hashmask];
and a5,a5,a4 # tmp358, tmp367, __futex_data.hashmask
which isn't too far from what runtime_const_mask_32() implements
where "lla + ld" sequence gets replaced by the "lui + addi"
sequence to load the immediate.
Sure it can be better here since we know the bitmask is of the form
GENMASK(N,0) but IMO runtime_const_mask_32() should generally work
for all masks.
Now, runtime_const_mask_lower_32(val, nbits) may be a better suited
API name for that purpose.
If there is enough interest, I'll go back to the drawing board and
go that route for v2 for arm64 and riscv.
--
Thanks and Regards,
Prateek
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-03-17 5:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 5:23 [RFC PATCH v2 0/7] futex: Use runtime constants for futex_hash computation K Prateek Nayak
2026-03-16 5:23 ` [RFC PATCH v2 1/7] x86/runtime-const: Introduce runtime_const_mask_32() K Prateek Nayak
2026-03-16 5:23 ` [RFC PATCH v2 2/7] arm64/runtime-const: " K Prateek Nayak
2026-03-16 11:50 ` David Laight
2026-03-16 17:09 ` K Prateek Nayak
2026-03-16 5:23 ` [RFC PATCH v2 3/7] arm64/runtime-const: Use aarch64_insn_patch_text_nosync() for patching K Prateek Nayak
2026-03-16 11:52 ` David Laight
2026-03-16 17:13 ` K Prateek Nayak
2026-03-16 5:23 ` [RFC PATCH v2 4/7] riscv/runtime-const: Introduce runtime_const_mask_32() K Prateek Nayak
2026-03-16 5:23 ` [RFC PATCH v2 5/7] s390/runtime-const: " K Prateek Nayak
2026-03-16 19:19 ` Heiko Carstens
2026-03-17 1:55 ` K Prateek Nayak
2026-03-16 5:24 ` [RFC PATCH v2 6/7] asm-generic/runtime-const: Add dummy runtime_const_mask_32() K Prateek Nayak
2026-03-16 5:24 ` [RFC PATCH v2 7/7] futex: Use runtime constants for __futex_hash() hot path K Prateek Nayak
2026-03-16 8:14 ` Sebastian Andrzej Siewior
2026-03-16 17:15 ` K Prateek Nayak
2026-03-17 3:06 ` Samuel Holland
2026-03-17 5:11 ` K Prateek Nayak [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=9fa8ef20-1da2-48e3-a9d8-340a5106cea8@amd.com \
--to=kprateek.nayak@amd.com \
--cc=agordeev@linux.ibm.com \
--cc=alex@ghiti.fr \
--cc=andrealmeid@igalia.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=borntraeger@linux.ibm.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=charlie@rivosinc.com \
--cc=cmirabil@redhat.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=jszhang@kernel.org \
--cc=kas@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=palmer@dabbelt.com \
--cc=peterz@infradead.org \
--cc=pjw@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=seanjc@google.com \
--cc=svens@linux.ibm.com \
--cc=tglx@kernel.org \
--cc=thuth@redhat.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
/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