From: John Kacur <jkacur@gmail.com>
To: Tomas Glozar <tglozar@redhat.com>
Cc: John Kacur <jkacur@redhat.com>,
linux-rt-users@vger.kernel.org,
Clark Williams <williams@redhat.com>
Subject: Re: [PATCH 6/6] rteval: Add --housekeeping option to reserve isolated CPUs
Date: Mon, 20 Apr 2026 17:42:18 -0400 (EDT) [thread overview]
Message-ID: <5d7d7ca2-514e-4d1f-7440-4333d415bcad@gmail.com> (raw)
In-Reply-To: <CAP4=nvQLbPBhQva-fBqeC1_ApGDYmNG7tSzuBNxMFg-EiFp7ag@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2051 bytes --]
On Mon, 20 Apr 2026, Tomas Glozar wrote:
> pá 17. 4. 2026 v 21:51 odesílatel John Kacur <jkacur@redhat.com> napsal:
> >
> > Add a new --housekeeping option that allows users to specify isolated CPUs
> > that should be reserved for system housekeeping tasks and not used by
> > rteval's measurement or load modules.
> >
> > Key features:
> > - Validates that housekeeping CPUs are in the isolated CPU list (isolcpus)
> > - Detects conflicts with explicitly specified --measurement-cpulist or
> > --loads-cpulist options and exits with a clear error message
> > - Filters housekeeping CPUs from both measurement and load CPU lists
> > - Correctly excludes housekeeping CPUs from inverted CPU lists when only
> > one of measurement/loads is specified
> >
> > Example usage:
> > rteval --housekeeping 0-3 --measurement-run-on-isolcpus
> > Reserves isolcpus 0-3 for system tasks, runs measurements on
> > remaining isolated CPUs (4+) plus non-isolated CPUs
> >
> > Implementation:
> > - systopology.py: Add validate_housekeeping_cpus() function to validate
> > that housekeeping CPUs are in isolcpus
> > - rteval-cmd: Add --housekeeping argument, conflict checking, filtering,
> > and fix inversion logic to exclude housekeeping CPUs
> >
>
> This might be a good opportunity to additionally pin the rteval
> process to the housekeeping CPUs, as well as pass them to rtla's -H
> option.
>
> Tomas
You raise good points. Currently, housekeeping CPUs are for system tasks
like kernel threads, IRQs, etc., and the --housekeeping flag tells
rteval
not to touch these CPUs. For example, you might have CPUs 0-7 isolated,
and use 0-1 for housekeeping, and 2-7 for measurement threads which are
already pinned in rteval with sched_affinity.
However, we currently don't:
1. Pin the rteval process itself to housekeeping CPUs
2. Pass them to timerlat's -H option
These would be useful enhancements to improve isolation further. I'll
consider adding them in a future update.
Thanks for the suggestions!
John Kacur
prev parent reply other threads:[~2026-04-20 21:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 19:51 [PATCH 0/6] rteval: Improve CPU management infrastructure and add housekeeping option John Kacur
2026-04-17 19:51 ` [PATCH 1/6] rteval: Add cpuset module for cgroup v2 management John Kacur
2026-04-17 19:51 ` [PATCH 2/6] rteval: Fix xmlout unit test XSL file path John Kacur
2026-04-17 19:51 ` [PATCH 3/6] rteval: Add CpuList class to cpulist_utils module John Kacur
2026-04-17 19:51 ` [PATCH 4/6] rteval: Migrate call sites to use CpuList class where beneficial John Kacur
2026-04-17 19:51 ` [PATCH 5/6] rteval: Add unit tests for CpuList class John Kacur
2026-04-17 19:51 ` [PATCH 6/6] rteval: Add --housekeeping option to reserve isolated CPUs John Kacur
2026-04-20 9:33 ` Tomas Glozar
2026-04-20 21:42 ` John Kacur [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=5d7d7ca2-514e-4d1f-7440-4333d415bcad@gmail.com \
--to=jkacur@gmail.com \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglozar@redhat.com \
--cc=williams@redhat.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