dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] drm/sched: Fix inverted comment for hang_limit
@ 2021-05-28 23:51 Alyssa Rosenzweig
  2021-06-01 15:59 ` Daniel Vetter
  0 siblings, 1 reply; 2+ messages in thread
From: Alyssa Rosenzweig @ 2021-05-28 23:51 UTC (permalink / raw)
  To: dri-devel; +Cc: David Airlie, Alyssa Rosenzweig

The hang_limit is the threshold after which the kernel no longer
attempts to schedule a job. Its documentation stated the opposite due to
a typo. Correct the wording to indicate the actual purpose of the field.

Signed-off-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
Cc: David Airlie <airlied@linux.ie>
Cc: Daniel Vetter <daniel@ffwll.ch>
---
 include/drm/gpu_scheduler.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/drm/gpu_scheduler.h b/include/drm/gpu_scheduler.h
index 10225a0a3..d18af49fd 100644
--- a/include/drm/gpu_scheduler.h
+++ b/include/drm/gpu_scheduler.h
@@ -275,7 +275,7 @@ struct drm_sched_backend_ops {
  * @pending_list: the list of jobs which are currently in the job queue.
  * @job_list_lock: lock to protect the pending_list.
  * @hang_limit: once the hangs by a job crosses this limit then it is marked
- *              guilty and it will be considered for scheduling further.
+ *              guilty and it will no longer be considered for scheduling.
  * @score: score to help loadbalancer pick a idle sched
  * @_score: score used when the driver doesn't provide one
  * @ready: marks if the underlying HW is ready to work
-- 
2.30.2


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] drm/sched: Fix inverted comment for hang_limit
  2021-05-28 23:51 [PATCH] drm/sched: Fix inverted comment for hang_limit Alyssa Rosenzweig
@ 2021-06-01 15:59 ` Daniel Vetter
  0 siblings, 0 replies; 2+ messages in thread
From: Daniel Vetter @ 2021-06-01 15:59 UTC (permalink / raw)
  To: Alyssa Rosenzweig; +Cc: David Airlie, dri-devel

On Fri, May 28, 2021 at 07:51:52PM -0400, Alyssa Rosenzweig wrote:
> The hang_limit is the threshold after which the kernel no longer
> attempts to schedule a job. Its documentation stated the opposite due to
> a typo. Correct the wording to indicate the actual purpose of the field.
> 
> Signed-off-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
> Cc: David Airlie <airlied@linux.ie>
> Cc: Daniel Vetter <daniel@ffwll.ch>

Not a drm/scheduler expert myself, but makes more sense than what's there.

Thanks for your patch, pushed to drm-misc-next.
-Daniel

> ---
>  include/drm/gpu_scheduler.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/drm/gpu_scheduler.h b/include/drm/gpu_scheduler.h
> index 10225a0a3..d18af49fd 100644
> --- a/include/drm/gpu_scheduler.h
> +++ b/include/drm/gpu_scheduler.h
> @@ -275,7 +275,7 @@ struct drm_sched_backend_ops {
>   * @pending_list: the list of jobs which are currently in the job queue.
>   * @job_list_lock: lock to protect the pending_list.
>   * @hang_limit: once the hangs by a job crosses this limit then it is marked
> - *              guilty and it will be considered for scheduling further.
> + *              guilty and it will no longer be considered for scheduling.
>   * @score: score to help loadbalancer pick a idle sched
>   * @_score: score used when the driver doesn't provide one
>   * @ready: marks if the underlying HW is ready to work
> -- 
> 2.30.2
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-06-01 15:59 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-05-28 23:51 [PATCH] drm/sched: Fix inverted comment for hang_limit Alyssa Rosenzweig
2021-06-01 15:59 ` Daniel Vetter

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).