Re: [PATCH drm-misc-next v2] drm/sched: implement dynamic job-flow control

2023-10-27 Thread Boris Brezillon
Hi Danilo, On Tue, 24 Oct 2023 00:57:47 +0200 Danilo Krummrich wrote: > > > + > > > + /** > > > + * @update_job_credits: Called once the scheduler is considering this > > > + * job for execution. > > > + * > > > + * Drivers may use this to update the job's submission credits, which is > > >

Re: [PATCH drm-misc-next v2] drm/sched: implement dynamic job-flow control

2023-10-23 Thread Luben Tuikov
On 2023-10-23 18:35, Danilo Krummrich wrote: > On Wed, Oct 11, 2023 at 09:52:36PM -0400, Luben Tuikov wrote: >> Hi, >> >> Thanks for fixing the title and submitting a v2 of this patch. Comments >> inlined below. >> >> On 2023-10-09 18:35, Danilo Krummrich wrote: >>> Currently, job flow control is

Re: [PATCH drm-misc-next v2] drm/sched: implement dynamic job-flow control

2023-10-23 Thread Luben Tuikov
On 2023-10-23 18:57, Danilo Krummrich wrote: > On Tue, Oct 10, 2023 at 09:41:51AM +0200, Boris Brezillon wrote: >> On Tue, 10 Oct 2023 00:35:53 +0200 >> Danilo Krummrich wrote: >> >>> Currently, job flow control is implemented simply by limiting the number >>> of jobs in flight. Therefore, a

Re: [PATCH drm-misc-next v2] drm/sched: implement dynamic job-flow control

2023-10-23 Thread Danilo Krummrich
On Tue, Oct 10, 2023 at 09:41:51AM +0200, Boris Brezillon wrote: > On Tue, 10 Oct 2023 00:35:53 +0200 > Danilo Krummrich wrote: > > > Currently, job flow control is implemented simply by limiting the number > > of jobs in flight. Therefore, a scheduler is initialized with a > > submission limit

Re: [PATCH drm-misc-next v2] drm/sched: implement dynamic job-flow control

2023-10-23 Thread Danilo Krummrich
On Wed, Oct 11, 2023 at 09:52:36PM -0400, Luben Tuikov wrote: > Hi, > > Thanks for fixing the title and submitting a v2 of this patch. Comments > inlined below. > > On 2023-10-09 18:35, Danilo Krummrich wrote: > > Currently, job flow control is implemented simply by limiting the number > > of

Re: [PATCH drm-misc-next v2] drm/sched: implement dynamic job-flow control

2023-10-13 Thread Luben Tuikov
On 2023-10-11 22:10, Danilo Krummrich wrote: > > > On 10/12/23 03:52, Luben Tuikov wrote: >> Hi, >> >> Thanks for fixing the title and submitting a v2 of this patch. Comments >> inlined below. >> >> On 2023-10-09 18:35, Danilo Krummrich wrote: >>> Currently, job flow control is implemented

Re: [PATCH drm-misc-next v2] drm/sched: implement dynamic job-flow control

2023-10-11 Thread Danilo Krummrich
On 10/12/23 03:52, Luben Tuikov wrote: Hi, Thanks for fixing the title and submitting a v2 of this patch. Comments inlined below. On 2023-10-09 18:35, Danilo Krummrich wrote: Currently, job flow control is implemented simply by limiting the number of jobs in flight. Therefore, a scheduler

Re: [PATCH drm-misc-next v2] drm/sched: implement dynamic job-flow control

2023-10-11 Thread Luben Tuikov
Hi, Thanks for fixing the title and submitting a v2 of this patch. Comments inlined below. On 2023-10-09 18:35, Danilo Krummrich wrote: > Currently, job flow control is implemented simply by limiting the number > of jobs in flight. Therefore, a scheduler is initialized with a > submission limit

Re: [PATCH drm-misc-next v2] drm/sched: implement dynamic job-flow control

2023-10-10 Thread Boris Brezillon
On Tue, 10 Oct 2023 00:35:53 +0200 Danilo Krummrich wrote: > Currently, job flow control is implemented simply by limiting the number > of jobs in flight. Therefore, a scheduler is initialized with a > submission limit that corresponds to the number of jobs which can be > sent to the hardware. >

[PATCH drm-misc-next v2] drm/sched: implement dynamic job-flow control

2023-10-09 Thread Danilo Krummrich
Currently, job flow control is implemented simply by limiting the number of jobs in flight. Therefore, a scheduler is initialized with a submission limit that corresponds to the number of jobs which can be sent to the hardware. This implies that for each job, drivers need to account for the