<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - CPU iowait higher when run the GPU multi decoding threads"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109830#c20">Comment # 20</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - CPU iowait higher when run the GPU multi decoding threads"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109830">bug 109830</a>
from <span class="vcard"><a class="email" href="mailto:owen.zhang@intel.com" title="Owen Zhang <owen.zhang@intel.com>"> <span class="fn">Owen Zhang</span></a>
</span></b>
<pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=109830#c18">comment #18</a>)
<span class="quote">> If you s/io_schedule_timeout/schedule_timeout/ inside i915.ko and the iowait
> remains... The iowait itself is nothing to do with us and we are just a
> victim; merely a symptom -- and in all likelihood that iowait goes down is
> indicative that _we_ regressed and are preventing the system from waiting
> for io elsewhere by keeping it busy instead.</span >
from my test, the change io_schedule_timeout to schedule_timeout in drm-tip, it
can see the iowait value changes to down, but can't work on linux 4.19.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>