From: "John B. Wyatt IV" <jwyatt@redhat.com>
To: Gabriele Monaco <gmonaco@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Waiman Long <longman@redhat.com>
Subject: Re: [PATCH v11 0/8] timers: Exclude isolated cpus from timer migration
Date: Wed, 27 Aug 2025 15:52:27 -0400 [thread overview]
Message-ID: <aK9h-_1jO_pHSmLS@thinkpad2024> (raw)
In-Reply-To: <20250808160142.103852-1-gmonaco@redhat.com>
On Fri, Aug 08, 2025 at 06:01:34PM +0200, Gabriele Monaco wrote:
> The timer migration mechanism allows active CPUs to pull timers from
> idle ones to improve the overall idle time. This is however undesired
> when CPU intensive workloads run on isolated cores, as the algorithm
> would move the timers from housekeeping to isolated cores, negatively
> affecting the isolation.
>
> Exclude isolated cores from the timer migration algorithm, extend the
> concept of unavailable cores, currently used for offline ones, to
> isolated ones:
> * A core is unavailable if isolated or offline;
> * A core is available if non isolated and online;
Hello Gabriele,
I tested your v11 patchset against 6.17-rc1-rt1 to see if it was the same issue with rtla-onoise getting latencies in the 20,000-40000 us on RHEL 10.2. It seems to have resolved the issue. Adding my tested-by tags and test results.
rtla osnoise top -c 1 -e sched:sched_switch -s 20 -T 1 -t -d 30m -q
CPU Period Runtime Noise % CPU Aval Max Noise Max Single HW NMI IRQ Softirq Thread
1 #1799 1799000003 3382675 99.81196 2840 9 1578 0 1799012 0 24369
Tested-by: John B. Wyatt IV <jwyatt@redhat.com>
Tested-by: John B. Wyatt IV <sageofredondo@gmail.com>
--
Sincerely,
John Wyatt
Software Engineer, Core Kernel
Red Hat
prev parent reply other threads:[~2025-08-27 19:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 16:01 [PATCH v11 0/8] timers: Exclude isolated cpus from timer migration Gabriele Monaco
2025-08-08 16:01 ` [PATCH v11 1/8] timers/migration: Postpone online/offline callbacks registration to late initcall Gabriele Monaco
2025-08-08 16:01 ` [PATCH v11 2/8] timers: Rename tmigr 'online' bit to 'available' Gabriele Monaco
2025-08-08 16:01 ` [PATCH v11 3/8] timers: Add the available mask in timer migration Gabriele Monaco
2025-08-08 16:01 ` [PATCH v11 4/8] timers: Use scoped_guard when setting/clearing the tmigr available flag Gabriele Monaco
2025-08-08 16:01 ` [PATCH v11 5/8] cgroup/cpuset: Rename update_unbound_workqueue_cpumask() to update_exclusion_cpumasks() Gabriele Monaco
2025-08-08 16:01 ` [PATCH v11 6/8] sched/isolation: Force housekeeping if isolcpus and nohz_full don't leave any Gabriele Monaco
2025-08-12 15:29 ` Waiman Long
2025-09-02 12:19 ` Frederic Weisbecker
2025-08-08 16:01 ` [PATCH v11 7/8] cgroup/cpuset: Fail if isolated and nohz_full don't leave any housekeeping Gabriele Monaco
2025-08-12 15:40 ` Waiman Long
2025-08-12 16:41 ` Waiman Long
2025-08-08 16:01 ` [PATCH v11 8/8] timers: Exclude isolated cpus from timer migration Gabriele Monaco
2025-08-12 17:20 ` Waiman Long
2025-08-13 15:20 ` Gabriele Monaco
2025-09-01 12:41 ` Frederic Weisbecker
2025-09-01 13:48 ` Gabriele Monaco
2025-09-01 21:11 ` Frederic Weisbecker
2025-09-02 11:08 ` Gabriele Monaco
2025-09-02 12:45 ` Frederic Weisbecker
2025-09-08 8:35 ` Gabriele Monaco
2025-08-27 19:52 ` John B. Wyatt IV [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=aK9h-_1jO_pHSmLS@thinkpad2024 \
--to=jwyatt@redhat.com \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=gmonaco@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--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