Author vstinner
Recipients gvanrossum, neologix, pitrou, python-dev, serhiy.storchaka, vstinner
Date 2014-01-23.21:39:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390513193.08.0.534894544523.issue20311@psf.upfronthosting.co.za>
In-reply-to
Content
> Those failures are "expected", nothing guarantees that the syscall
> will take at least the amount of time specified.

Ah? The manual page of epoll_wait() says:

"The  timeout  argument specifies the minimum number of milliseconds that epoll_wait() will block.  (This interval will be rounded up to the system clock granularity, and kernel scheduling delays mean that the blocking  interval may  overrun  by  a  small  amount.)"

I read minimum, not maximum here :-)

If epoll_wait(timeout_ms) may wait less than timeout_ms seconds, asyncio algorithm is wrong, or at least inefficient. It should loop until the time delta is at least total_timeout seconds. See the original issue:
http://code.google.com/p/tulip/issues/detail?id=106
History
Date User Action Args
2014-01-23 21:39:53vstinnersetrecipients: + vstinner, gvanrossum, pitrou, neologix, python-dev, serhiy.storchaka
2014-01-23 21:39:53vstinnersetmessageid: <1390513193.08.0.534894544523.issue20311@psf.upfronthosting.co.za>
2014-01-23 21:39:53vstinnerlinkissue20311 messages
2014-01-23 21:39:52vstinnercreate