From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: David Aldrich <david.aldrich.ntml@gmail.com>, lttng-dev@lists.lttng.org
Cc: Frederic Weisbecker <frederic@kernel.org>
Subject: Re: A question regarding isolated cpus and software interrupts
Date: Fri, 30 May 2025 10:49:20 -0400 [thread overview]
Message-ID: <93e83ed5-bcf3-4a5e-b713-4f9612ff7a6d@efficios.com> (raw)
In-Reply-To: <CAJK_iej1UnwTBaJCY0WwP2g=zqEMtphgM2DUJhtKmHxNceD3yw@mail.gmail.com>
On 2025-05-29 14:06, David Aldrich via lttng-dev wrote:
> Hi
>
> My question isn't directly related to lttng but I would welcome some advice.
>
> Our Linux application is showing 'blips' whereby there are occasional
> increases in processing times. This is for a user process that runs on
> an isolated core. Using lttng and TraceCompass I have found that the
> 'blip' sometimes coincides with a TIMER_SOFTIRQ event on the isolated
> core.
>
> I was surprised that software interrupts may run on isolated cores. Is
> there a way of preventing this?
+CC Frederic Weisbecker.
How are the cores isolated on your system (exact kernel command line
options or commands issued) ? There are various degree of fine-tuning
to prevent disturbance from the tick (nohz full), scheduling, and
irqs that can be done explicitly. So depending on your specific
configuration, you may be missing isolation options that would
prevent the softirq from running on your isolated cpus.
Thanks,
Mathieu
>
> Are there any techniques using lttng to gain more information related
> to the interrupt (e.g. what is causing it)?
>
> Best regards
> David
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next prev parent reply other threads:[~2025-05-30 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 18:06 David Aldrich via lttng-dev
2025-05-30 14:49 ` Mathieu Desnoyers via lttng-dev [this message]
2025-05-30 15:00 ` David Aldrich via lttng-dev
2025-06-17 10:52 Norbert Lange via lttng-dev
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=93e83ed5-bcf3-4a5e-b713-4f9612ff7a6d@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=david.aldrich.ntml@gmail.com \
--cc=frederic@kernel.org \
--cc=mathieu.desnoyers@efficios.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