Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: David Aldrich via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: Understanding SOFT IRQ 1
Date: Fri, 9 May 2025 17:00:17 +0100	[thread overview]
Message-ID: <CAJK_iegCiWpZcD8fyLCpkRtzOzv_nxyn8WBUs9gr5WDYQ1sK_w@mail.gmail.com> (raw)

Hi

I am just getting started with LTTng and Trace Compass. I can capture
Kernel and UST events.

My purpose is to investigate why a periodic task, running on an
isolated core, has occasional blips i.e. it's period (duration)
extends.

I have inserted tracepoints to mark normal and extended durations. In
Trace Compass the blip tracepoint is preceded by a brown state that is
'SOFT IRQ 1'. This extends down all cores. It lasts 105us and is
likely to be the reason for the blip.

Please could someone explain to me what may be happening here and how
can I find out the reason for this SOFT IRQ?

Best regards
David

             reply	other threads:[~2025-05-09 16:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-09 16:00 David Aldrich via lttng-dev [this message]
2025-05-12 15:18 ` Mathieu Desnoyers via lttng-dev
2025-05-12 15:41   ` Mathieu Desnoyers 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_iegCiWpZcD8fyLCpkRtzOzv_nxyn8WBUs9gr5WDYQ1sK_w@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