<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Double tap not always recognized"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90172#c21">Comment # 21</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Double tap not always recognized"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90172">bug 90172</a>
from <span class="vcard"><a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> <span class="fn">Peter Hutterer</span></a>
</span></b>
<pre>hard to be sure without profiling, but what I speculate is: input events and
the timerfd are both epoll sources in libinput. but input events are read in a
loop to pull all of them off the device, which can potentially starve the
timerfd. i.e. while the device keeps producing events as fast as we process
them, we never check the timerfd for timeouts and thus go past the allotted
time. the event processing doesn't double-check if the event time is newer than
a previously scheduled timer (it should, feel free to file a bug for this) so
we process an event that comes in late as within the timeout - simply because
we haven't checked the timeout yet.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>