From: Frederic Weisbecker <frederic@kernel.org>
To: Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"bigeasy@linutronix.de" <bigeasy@linutronix.de>,
"Preclik, Tobias" <tobias.preclik@siemens.com>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
"Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: Control of IRQ Affinities from Userspace
Date: Wed, 26 Nov 2025 16:45:38 +0100 [thread overview]
Message-ID: <aScgovATTqcdPmYB@localhost.localdomain> (raw)
In-Reply-To: <4de393b9304c99386d847ed0694ec12075a99c0a.camel@siemens.com>
Le Wed, Nov 26, 2025 at 10:20:53AM +0100, Florian Bezdeka a écrit :
> > drivers/net/ethernet/wangxun/libwx/wx_lib.c:1867: nvecs = pci_alloc_irq_vectors_affinity(wx->pdev, nvecs,
> > drivers/nvme/host/pci.c:2659: return pci_alloc_irq_vectors_affinity(pdev, 1, irq_queues, flags,
> > drivers/scsi/be2iscsi/be_main.c:3585: if (pci_alloc_irq_vectors_affinity(phba->pcidev, 2, nvec,
> > drivers/scsi/csiostor/csio_isr.c:520: cnt = pci_alloc_irq_vectors_affinity(hw->pdev, min, cnt,
> > drivers/scsi/hisi_sas/hisi_sas_v3_hw.c:2611: vectors = pci_alloc_irq_vectors_affinity(pdev,
> > drivers/scsi/megaraid/megaraid_sas_base.c:5943: i = pci_alloc_irq_vectors_affinity(instance->pdev,
> > drivers/scsi/mpi3mr/mpi3mr_fw.c:862: retval = pci_alloc_irq_vectors_affinity(mrioc->pdev,
> > drivers/scsi/mpt3sas/mpt3sas_base.c:3390: i = pci_alloc_irq_vectors_affinity(ioc->pdev,
> > drivers/scsi/pm8001/pm8001_init.c:982: rc = pci_alloc_irq_vectors_affinity(
> > drivers/scsi/qla2xxx/qla_isr.c:4539: ret = pci_alloc_irq_vectors_affinity(ha->pdev, min_vecs,
> > drivers/virtio/virtio_pci_common.c:160: err = pci_alloc_irq_vectors_affinity(vp_dev->pci_dev, nvectors,
> >
> > Not a so dead road :)
>
> Grml... I definitely fat-fingered the query. Anyway, this housekeeping
> API still seems very boot-time oriented to me. Can't see yet where this
> housekeeping cpumasks are filled up by the cgroup/cpuset infrastructure.
It's on the way:
https://lore.kernel.org/all/20251105210348.35256-1-frederic@kernel.org/
If all goes well, not for the upcoming merge window but the next one.
> cgroups/cpusets don't care about "isolation" in that sense yet. It's
> just about cpumasks for compute. Am I missing something?
It's a bit more than just scheduler domain isolation. It also handles
kthreads and workqueues. It's also going to handle unbound timers (on the way
to the upcoming merge window).
Thanks.
>
>
> Florian
--
Frederic Weisbecker
SUSE Labs
next prev parent reply other threads:[~2025-11-26 15:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 14:20 Control of IRQ Affinities from Userspace Preclik, Tobias
2025-11-03 15:53 ` Sebastian Andrzej Siewior
2025-11-03 17:12 ` Florian Bezdeka
2025-11-05 13:11 ` Preclik, Tobias
2025-11-05 13:18 ` Preclik, Tobias
2025-11-11 14:35 ` bigeasy
2025-11-11 14:34 ` bigeasy
2025-11-21 13:25 ` Preclik, Tobias
2025-11-24 9:59 ` bigeasy
2025-11-25 11:32 ` Florian Bezdeka
2025-11-25 11:50 ` bigeasy
2025-11-25 14:36 ` Florian Bezdeka
2025-11-25 16:31 ` Thomas Gleixner
2025-11-26 9:20 ` Florian Bezdeka
2025-11-26 14:26 ` Thomas Gleixner
2025-11-26 15:07 ` Florian Bezdeka
2025-11-26 19:15 ` Thomas Gleixner
2025-11-27 14:06 ` Preclik, Tobias
2025-11-27 14:52 ` Florian Bezdeka
2025-11-27 18:09 ` Thomas Gleixner
2025-11-28 7:33 ` Florian Bezdeka
2025-11-26 15:45 ` Frederic Weisbecker [this message]
2025-11-26 15:31 ` Frederic Weisbecker
2025-11-26 15:24 ` Frederic Weisbecker
2025-11-11 13:58 ` Sebastian Andrzej Siewior
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=aScgovATTqcdPmYB@localhost.localdomain \
--to=frederic@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=florian.bezdeka@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tobias.preclik@siemens.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.