From: Yury Norov <yury.norov@gmail.com>
To: linux-kernel@vger.kernel.org,
"Yury Norov [NVIDIA]" <yury.norov@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
John Stultz <jstultz@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Stephen Boyd <sboyd@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH v4 0/3] bitmap: introduce find_random_bit() and use in clocksource
Date: Thu, 19 Jun 2025 14:26:22 -0400 [thread overview]
Message-ID: <20250619182626.393541-1-yury.norov@gmail.com> (raw)
nodemasks implement node_random(), which may also be useful for other
subsystems. Generalize the function, and propagate to cpumask API.
v1: https://lore.kernel.org/all/20250604212125.25656-1-yury.norov@gmail.com/
v2: https://lore.kernel.org/all/20250608194536.28130-1-yury.norov@gmail.com/
v3: https://lore.kernel.org/all/20250617200854.60753-1-yury.norov@gmail.com/
v4: return NUMA_NO_NODES instead of MAX_NUMNODES in node_random() (Andrew)
Yury Norov [NVIDIA] (3):
bitmap: generalize node_random()
cpumask: introduce cpumask_random()
clocksource: Improve randomness in clocksource_verify_choose_cpus()
include/linux/cpumask.h | 12 ++++++++++++
include/linux/find.h | 2 ++
include/linux/nodemask.h | 18 +++---------------
kernel/time/clocksource.c | 5 +----
lib/find_bit.c | 24 ++++++++++++++++++++++++
5 files changed, 42 insertions(+), 19 deletions(-)
--
2.43.0
next reply other threads:[~2025-06-19 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 18:26 Yury Norov [this message]
2025-06-19 18:26 ` [PATCH v4 1/3] bitmap: generalize node_random() Yury Norov
2025-06-19 18:26 ` [PATCH v4 2/3] cpumask: introduce cpumask_random() Yury Norov
2025-06-19 18:26 ` [PATCH v4 3/3] clocksource: Improve randomness in clocksource_verify_choose_cpus() Yury Norov
2025-06-20 21:37 ` [PATCH v4 0/3] bitmap: introduce find_random_bit() and use in clocksource Thomas Gleixner
2025-06-21 14:21 ` Yury Norov
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=20250619182626.393541-1-yury.norov@gmail.com \
--to=yury.norov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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®