From: Philipp Stanner <phasta@mailbox.org>
To: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>,
phasta@kernel.org, dri-devel@lists.freedesktop.org
Cc: kernel-dev@igalia.com, intel-xe@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Matthew Brost" <matthew.brost@intel.com>
Subject: Re: [PATCH] drm/sched: Simplify idle entity check
Date: Fri, 09 Jan 2026 15:48:09 +0100 [thread overview]
Message-ID: <a51103108eaa84134591c8321c6a70a484daed2b.camel@mailbox.org> (raw)
In-Reply-To: <607847da-4f8a-4c19-9ebe-c07f79ce1362@igalia.com>
On Fri, 2026-01-09 at 14:06 +0000, Tvrtko Ursulin wrote:
> \
> On 07/01/2026 14:11, Philipp Stanner wrote:
> > Happy 2026, Tvrtko!
> >
> >
[…]
> > Not to long ago we discussed that the spsc_queue should be removed and
> > replaced by some sort of list, with proper locks. Christian has agreed
> > that this should fly.
> >
> > The spsc queue has only 1 user in the kernel and it's super hard to
> > understand how it's supposed to work and when any why barriers and
> > READ_ONCE's are necessary (that's, of course, also not documented in
> > the queue).
> >
> > Until that is done I don't really want to touch any of those memory
> > barriers..
>
> (I had a branch with spsc gone more than a year ago but I abandoned it
> for now since it contained some other too ambitious changes. So no
> complaints from me. Who is doing it BTW?)
No one is working on it.
But I think the discussion has succeeded. The only objector was
Christian because he was worried about some cache-line performance
regression. I can't remember for sure, but I think Christian realized
that cache lines are not an issue (with a hlist?).
If you want to pick up removing SPSC-queue, be my guest, but make sure
to discuss it with Christian before investing too much of your time.
>
> Back to the point - this patch can wait, no problem. To explain the
> context though.
>
> I wanted to get rid of looking at the list_empty here because I have a
> branch which improves the flow for the 1:1 sched:entity drivers.
>
> Why are the two related? If you remember in the fair scheduler series
> all the run-queue stuff is nicely grouped in sched_rq.c and encapsulated
> in the rq API, which made it possible to follow up with virtualizing the
> rq operations.
>
> The yet another relevant thing is the patch I sent this week which
> removes the special case where entity can be initialized with no schedulers.
>
> If we combined all these three pre-requisites, my branch allows the
> fully invariant sched:entity and 1:1:1 sched:rq:entity. Run-queue vfuncs
Hm, wouldn't the CFS series annihilate multiple RQs anyways? This
sounds as if there are several series' floating around, cleaning up
similar things.
P.
next prev parent reply other threads:[~2026-01-12 13:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 13:44 [PATCH] drm/sched: Simplify idle entity check Tvrtko Ursulin
2026-01-07 13:50 ` ✗ CI.checkpatch: warning for " Patchwork
2026-01-07 13:51 ` ✓ CI.KUnit: success " Patchwork
2026-01-07 14:08 ` [PATCH] " Danilo Krummrich
2026-01-09 14:08 ` Danilo Krummrich
2026-01-07 14:11 ` Philipp Stanner
2026-01-09 14:06 ` Tvrtko Ursulin
2026-01-09 14:31 ` Christian König
2026-01-15 13:30 ` Tvrtko Ursulin
2026-01-09 14:48 ` Philipp Stanner [this message]
2026-01-09 15:11 ` Christian König
2026-01-12 10:35 ` Tvrtko Ursulin
2026-01-07 14:29 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-01-07 16:32 ` ✗ Xe.CI.Full: failure " Patchwork
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=a51103108eaa84134591c8321c6a70a484daed2b.camel@mailbox.org \
--to=phasta@mailbox.org \
--cc=christian.koenig@amd.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=kernel-dev@igalia.com \
--cc=matthew.brost@intel.com \
--cc=phasta@kernel.org \
--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