From: David Aldrich via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: A question regarding isolated cpus and software interrupts
Date: Thu, 29 May 2025 19:06:31 +0100 [thread overview]
Message-ID: <CAJK_iej1UnwTBaJCY0WwP2g=zqEMtphgM2DUJhtKmHxNceD3yw@mail.gmail.com> (raw)
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?
Are there any techniques using lttng to gain more information related
to the interrupt (e.g. what is causing it)?
Best regards
David
next reply other threads:[~2025-05-30 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 18:06 David Aldrich via lttng-dev [this message]
2025-05-30 14:49 ` Mathieu Desnoyers via lttng-dev
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='CAJK_iej1UnwTBaJCY0WwP2g=zqEMtphgM2DUJhtKmHxNceD3yw@mail.gmail.com' \
--to=lttng-dev@lists.lttng.org \
--cc=david.aldrich.ntml@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