<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Am 12.07.2017 um 17:53 schrieb Jason
Ekstrand:<br>
</div>
<blockquote type="cite"
cite="mid:CAOFGe95mj1G_Ap0oOPFyatZWEbEk_Kwo8Wn_E+eYS16Nhz_huQ@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">[SNIP]<br>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">
</span>Is that easier than just waiting in the kernel, I'm
not sure how<br>
optimised we need this path to be.<span class="HOEnZb"><font
color="#888888"><br>
</font></span></blockquote>
</div>
<br>
</div>
<div class="gmail_extra">I don't think so. I think it's
more-or-less the same code regardless of how it's done. The
advantage of doing it in the kernel is that it's standardized
(we don't have to both go write that userspace code) and it
doesn't have the problems stated above.<br>
</div>
</div>
</blockquote>
<br>
Ok, I'm convinced. The next price question is then how do we do it?<br>
<br>
I mean writing an IOCTL to wait for a fence to appear is simple, but
do we also need to wait for a fence to change?<br>
<br>
As long as waits don't consume fences that might be rather tricky.<br>
<br>
Christian.<br>
</body>
</html>