From: I Hsin Cheng <richard120310@gmail.com>
To: yury.norov@gmail.com
Cc: linux@rasmusvillemoes.dk, jstultz@google.com, tglx@linutronix.de,
sboyd@kernel.org, linux-kernel@vger.kernel.org,
eleanor15x@gmail.com, visitorckw@gmail.com,
jserv@ccns.ncku.edu.tw, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linux.dev,
I Hsin Cheng <richard120310@gmail.com>
Subject: [RFC PATCH 0/2] Introduce cpumask_first_but() and use cases
Date: Fri, 13 Jun 2025 11:34:45 +0800 [thread overview]
Message-ID: <20250613033447.3531709-1-richard120310@gmail.com> (raw)
This series introduce cpumask_first_but() and make cpumask_any_but()
a wrapper around it, just like other cpumask_any*() helpers, they're
some wrappers around cpumask_first*(), except some special cases.
The patches are scheduled as the following:
1. The implementation of cpumask_first_but() and some
positive results of making cpumask_any_but() a wrapper around
it are attached there, including performance and code size.
2. Use cpumask_first_but() in clocksource
I Hsin Cheng (2):
cpumask: Introduce cpumask_first_but()
clocksource: Use cpumask_first_but() in
clocksource_verify_choose_cpus()
include/linux/cpumask.h | 22 ++++++++++++++++------
kernel/time/clocksource.c | 4 +---
2 files changed, 17 insertions(+), 9 deletions(-)
--
2.43.0
next reply other threads:[~2025-06-13 3:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 3:34 I Hsin Cheng [this message]
2025-06-13 3:34 ` [RFC PATCH 1/2] cpumask: Introduce cpumask_first_but() I Hsin Cheng
2025-06-13 5:55 ` Kuan-Wei Chiu
2025-06-13 3:34 ` [RFC PATCH 2/2] clocksource: Use cpumask_first_but() in clocksource_verify_choose_cpus() I Hsin Cheng
2025-06-13 5:02 ` Yury Norov
2025-06-13 5:22 ` I Hsin Cheng
2025-06-16 14:34 ` Shuah Khan
2025-06-13 5:41 ` I Hsin Cheng
2025-06-13 6:00 ` I Hsin Cheng
2025-06-13 10:48 ` Thomas Gleixner
2025-06-13 11:37 ` I Hsin Cheng
2025-06-13 16:29 ` Yury Norov
2025-06-13 16:56 ` Thomas Gleixner
2025-06-16 14:38 ` Shuah Khan
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=20250613033447.3531709-1-richard120310@gmail.com \
--to=richard120310@gmail.com \
--cc=eleanor15x@gmail.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=jstultz@google.com \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=sboyd@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tglx@linutronix.de \
--cc=visitorckw@gmail.com \
--cc=yury.norov@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