From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH] drm/i915: Bump priority of clean up work
Date: Mon, 13 Aug 2018 15:49:43 +0300 [thread overview]
Message-ID: <87h8jy4ejc.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <153415721543.23925.11458276137875973105@skylake-alporthouse-com>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Quoting Chris Wilson (2018-07-12 12:57:29)
>> We require that we keep the list of outstanding work short so that we do
>> not "leak" memory while pageflipping under stress. However that system
>> stress may delay kernel workers virtually indefinitely, which incurs the
>> pageflips stall and eventually hit a timeout waiting for the cleanup.
>>
>> Try to combat CPU starvation of our short-lived cleanup workers by
>> switching to a high priority workqueue.
>>
>> Testcase: igt/kms_cursor_legacy/all-pipes-torture-move
>> References: https://bugs.freedesktop.org/show_bug.cgi?id=107122
>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
>> ---
>> Not sure if highpri is enough to combat our RT torture...
>
> CI thinks it is.
Not so familiar with the atomic commit. But it makes
sense and now there is evidence supporting it.
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> -Chris
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-08-13 12:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 11:57 [PATCH] drm/i915: Bump priority of clean up work Chris Wilson
2018-07-12 13:26 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-08-11 10:03 ` Patchwork
2018-08-11 10:51 ` ✓ Fi.CI.IGT: " Patchwork
2018-08-11 10:53 ` Chris Wilson
2018-08-13 9:18 ` ✓ Fi.CI.BAT: " Patchwork
2018-08-13 10:44 ` ✓ Fi.CI.IGT: " Patchwork
2018-08-13 10:46 ` [PATCH] " Chris Wilson
2018-08-13 12:49 ` Mika Kuoppala [this message]
2018-08-13 13:00 ` Chris Wilson
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=87h8jy4ejc.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.