From: "Ionut Nechita (Sunlight Linux)" <sunlightlinux@gmail.com>
To: tglx@kernel.org
Cc: anna-maria@linutronix.de, frederic@kernel.org,
ionut_n2001@yahoo.com, linux-kernel@vger.kernel.org,
mingo@kernel.org, sunlightlinux@gmail.com
Subject: Re: [PATCH 1/1] tick/nohz: Add fast-path tick stopping for idle isolated cores
Date: Mon, 26 Jan 2026 21:31:09 +0200 [thread overview]
Message-ID: <20260126193108.6501-2-sunlightlinux@gmail.com> (raw)
In-Reply-To: <873449g79w.ffs@tglx>
From: Ionut Nechita <sunlightlinux@gmail.com>
On Tue, Jan 13 2026 at 11:02, Thomas Gleixner wrote:
> You can avoid the per bit evaluation way simpler, which improves the
> evaluation independent of context. See uncompiled patch below.
Thank you for the detailed feedback and for taking the time to review
this patch.
Your approach is indeed much simpler and more elegant. I see no issues
with it, and it has the additional benefit of improving the evaluation
regardless of context, rather than being restricted to nohz_full CPUs
and the idle task. This is clearly a better solution.
I appreciate the learning opportunity - working on kernel development
continues to teach me new and interesting things every day.
Should I prepare a v2 based on your suggestion, or would you prefer to
submit this as a separate patch?
Thanks again,
Ionut
next prev parent reply other threads:[~2026-01-26 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 15:36 [PATCH 0/1] tick/nohz: Optimize tick stopping for isolated cores Ionut Nechita (Sunlight Linux)
2026-01-06 15:36 ` [PATCH 1/1] tick/nohz: Add fast-path tick stopping for idle " Ionut Nechita (Sunlight Linux)
2026-01-13 10:02 ` Thomas Gleixner
2026-01-26 19:31 ` Ionut Nechita (Sunlight Linux) [this message]
2026-01-26 21:32 ` Thomas Gleixner
2026-01-27 13:40 ` Frederic Weisbecker
2026-01-28 7:26 ` Ionut Nechita (Sunlight Linux)
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=20260126193108.6501-2-sunlightlinux@gmail.com \
--to=sunlightlinux@gmail.com \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=ionut_n2001@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@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