On 2023-10-31 22:23, Danilo Krummrich wrote:
> Hi Luben,
>
[snip]
>>> @@ -187,12 +251,14 @@ void drm_sched_rq_remove_entity(struct drm_sched_rq
>>> *rq,
>>> /**
>>> * drm_sched_rq_select_entity_rr - Select an entity which could provide a
>>> job to run
>>> *
>>> + * @sched: the gpu
Hi Luben,
On Tue, Oct 31, 2023 at 08:51:17PM -0400, Luben Tuikov wrote:
> Hi,
>
> (PSA: luben.tui...@amd.com should've bounced :-) I'm removing it from the To:
> field.)
>
> On 2023-10-30 20:26, Danilo Krummrich wrote:
> > Currently, job flow control is implemented simply by limiting the
Hi,
(PSA: luben.tui...@amd.com should've bounced :-) I'm removing it from the To:
field.)
On 2023-10-30 20:26, 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 credit
> limit that
On 10/31/23 12:13, Christian König wrote:
Am 31.10.23 um 01:26 schrieb Danilo Krummrich:
Currently, job flow control is implemented simply by limiting the number
of jobs in flight. Therefore, a scheduler is initialized with a credit
limit that corresponds to the number of jobs which can be
Am 31.10.23 um 01:26 schrieb Danilo Krummrich:
Currently, job flow control is implemented simply by limiting the number
of jobs in flight. Therefore, a scheduler is initialized with a credit
limit that corresponds to the number of jobs which can be sent to the
hardware.
This implies that for
: b2139fb5051554a7f297e4ad584ef1bc26c76d5d
patch link:
https://lore.kernel.org/r/20231031002655.38707-1-dakr%40redhat.com
patch subject: [PATCH drm-misc-next v4] drm/sched: implement dynamic job-flow
control
config: loongarch-randconfig-002-20231031
(https://download.01.org/0day-ci/archive/20231031/202310311632
: b2139fb5051554a7f297e4ad584ef1bc26c76d5d
patch link:
https://lore.kernel.org/r/20231031002655.38707-1-dakr%40redhat.com
patch subject: [PATCH drm-misc-next v4] drm/sched: implement dynamic job-flow
control
config: arc-randconfig-002-20231031
(https://download.01.org/0day-ci/archive/20231031/202310311534.i8wqwok0
Currently, job flow control is implemented simply by limiting the number
of jobs in flight. Therefore, a scheduler is initialized with a credit
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 maximum
