On Tue, 7 Oct 2025 16:44:59 +0200 Danilo Krummrich <d...@kernel.org> wrote:
> On 9/30/25 1:57 PM, Boris Brezillon wrote: > > Can you remind me what the problem is? I thought the lifetime issue was > > coming from the fact the drm_sched ownership model was lax enough that > > the job could be owned by both drm_gpu_scheduler and drm_sched_entity > > at the same time. > > I don't think that's (directly) a thing from the perspective of the drm_sched > design. A job should be either in the entity queue for the pending_list of the > scheduler. > > However, different drivers do implement their own lifetime (and ownership) > model > on top of that, because they ultimately have to deal with jobs being either > tied > to the entity or the scheduler lifetime, which is everything else but strait > forward in error cases and tear down paths. > > And the fundamental problem why drivers implement their own rules on top of > this > is because it is hard to deal with jobs being tied to entirely different > lifetime model depending on their state. > > So, what I'm saying is that from the perspective of the component itself it's > probably fine, but for the application in drivers it's the root cause for a > lot > of the hacks we see on top of the scheduler in drivers. > > Some of those hacks even make their way into the scheduler [1]. > > [1] > https://elixir.bootlin.com/linux/v6.17.1/source/drivers/gpu/drm/scheduler/sched_main.c#L1439 > > >> Instead, I think the new Jobqueue should always own and always dispatch > >> jobs > >> directly and provide some "control API" to be instructed by an external > >> component (orchestrator) on top of it when and to which ring to dispatch > >> jobs. > > > > Feels to me that we're getting back to a model where the JobQueue needs > > to know about the upper-layer in charge of the scheduling. I mean, it > > can work, but you're adding some complexity back to JobQueue, which I > > was expecting to be a simple FIFO with a dep-tracking logic. > > Yes, the Jobqueue would need an interface to the orchestrator. I rather have > the > complexity encapsulated in the Jobqueue, rather than pushing the complexity to > drivers by having a more complex lifetime and ownership model that leaks into > drivers as mentioned above. > > > I have a hard time seeing how it can fully integrate in this > > orchestrator model. We can hook ourselves in the JobQueue::run_job() > > and schedule the group for execution when we queue a job to the > > ringbuf, but the group scheduler would still be something on the side. > > Can you please expand a bit more on the group model? > > My understanding is that you have a limited number of firmware rings (R) and > each of those rings has N slots, where N is the number of queue types > supported > by the GPU. Honestly, the naming is a bit confusing, because for us, the ring buffer is what gets attached to each queue and contains the jobs to be executed on that queue. But other than this naming issue, that's pretty much it, yes. > > So, you need something that can schedule "groups" of queues over all available > firmware rings, because it would be pointless to schedule each individual > queue > independently, as a firmware ring has slots for each of those. Is that > correct? It's not just that it would be pointless, it's not even an option, because there are inter-queue synchronization mechanisms that only work if the queues belong to the same group.
