From: Tejun Heo <tj@kernel.org>
To: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
kernel-dev@igalia.com,
Boris Brezillon <boris.brezillon@collabora.com>,
Chia-I Wu <olv@google.com>, Liviu Dudau <liviu.dudau@arm.com>,
Matthew Brost <matthew.brost@intel.com>,
Steven Price <steven.price@arm.com>
Subject: Re: [PATCH v8 5/6] workqueue: Imply strict CPU affinity for WQ_RT
Date: Mon, 9 Nov 2026 04:24:43 -1000 [thread overview]
Message-ID: <avHXq1lK7m_Sfz2j@slm.duckdns.org> (raw)
In-Reply-To: <6b489363-274f-426a-9143-6ed5593a0c19@igalia.com>
Hello,
On Mon, Nov 09, 2026 at 09:52:17AM +0000, Tvrtko Ursulin wrote:
...
> apply_workqueue_attrs() would work in theory but is not exported for modules
> which is required for panthor.
Oh, please feel free to export them.
> Regarding the flag reorganization, what would require expanding to u64?
> Unless I am missing something I see currently only 20 bits are used.
Right, it might not be strictly necessary. Just something we might as well
do while at it if we want to encode a bunch of scope / attrs in the flags.
> Although on a higher level my feeling is that panthor could first try with
> WQ_RT as is, and we consider adding strict affinity, via either of the above
> options, if that will not be good enough.
I see.
Thanks.
--
tejun
next prev parent reply other threads:[~2026-11-09 14:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 9:52 [PATCH v8 0/6] Realtime workqueues and panthor realtime submission Tvrtko Ursulin
2026-11-04 9:52 ` [PATCH v8 1/6] workqueue: Simplify unbound sysfs attribute registration Tvrtko Ursulin
2026-11-04 9:52 ` [PATCH v8 2/6] workqueue: Separate sysfs mutable vs immutable wq attribute sanitizing Tvrtko Ursulin
2026-11-04 9:52 ` [PATCH v8 3/6] workqueue: Convert nice value tracking to priority based Tvrtko Ursulin
2026-11-04 9:52 ` [PATCH v8 4/6] workqueue: Add support for real-time workers Tvrtko Ursulin
2026-11-05 18:50 ` Tejun Heo
2026-11-09 9:42 ` Tvrtko Ursulin
2026-11-04 9:52 ` [PATCH v8 5/6] workqueue: Imply strict CPU affinity for WQ_RT Tvrtko Ursulin
2026-11-05 19:00 ` Tejun Heo
2026-11-09 9:52 ` Tvrtko Ursulin
2026-11-09 14:24 ` Tejun Heo [this message]
2026-11-04 9:52 ` [PATCH v8 6/6] drm/panthor: Create per queue priority workqueues Tvrtko Ursulin
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=avHXq1lK7m_Sfz2j@slm.duckdns.org \
--to=tj@kernel.org \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-dev@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=matthew.brost@intel.com \
--cc=olv@google.com \
--cc=steven.price@arm.com \
--cc=tvrtko.ursulin@igalia.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
all inboxes | Powered by JetHome®