On 1/13/20 5:08 PM, Ian Jackson wrote: > If a timer event callback causes this poller to be woken (not very > unlikely) we would go round the poll loop twice rather than once. > > Do the poller pipe emptying at the end; this is slightly more > efficient because it can't cause any callbacks, so it happens after > all the callbacks have been run. > > (This pipe-emptying has to happen in afterpoll rather than the > apparently more logical beforepoll, because the application calling > beforepoll doesn't constitute a promise to actually do anything.) > > Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com>
I can't quite figure out: why would you end up going around the loop twice, and how does this fix it? -George _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
