Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: David Aldrich via lttng-dev <lttng-dev@lists.lttng.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: lttng-dev@lists.lttng.org, Frederic Weisbecker <frederic@kernel.org>
Subject: Re: A question regarding isolated cpus and software interrupts
Date: Fri, 30 May 2025 16:00:23 +0100	[thread overview]
Message-ID: <CAJK_iehAs4seOuTxxrGtUmh92jA_kbwuphb=dcWm1DSDfpxEBw@mail.gmail.com> (raw)
In-Reply-To: <93e83ed5-bcf3-4a5e-b713-4f9612ff7a6d@efficios.com>

Hi Mathieu

Thanks for your reply.

> 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.

Our kernel parameters are:

ro skew_tick=1 rcu_nocb_poll rcu_nocbs=4-31 nohz=on nohz_full=4-31
kthread_cpus=0-3 irqaffinity=0-3 isolcpus=managed_irq,domain,4-31
intel_pstate=passive nosoftlockup tsc=nowatchdog intel_iommu=on
iommu=pt default_hugepagesz=1G hugepagesz=1G hugepages=4
vfio_pci.enable_sriov=1 vfio_pci.disable_idle_d3=1

(the affected thread runs on core 4).

Best regards
David

  reply	other threads:[~2025-05-30 15:02 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
2025-05-30 15:00   ` David Aldrich via lttng-dev [this message]
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_iehAs4seOuTxxrGtUmh92jA_kbwuphb=dcWm1DSDfpxEBw@mail.gmail.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