* looking for explanation of select() timeout behaviour
@ 2008-06-23 16:00 Chris Friesen
0 siblings, 0 replies; only message in thread
From: Chris Friesen @ 2008-06-23 16:00 UTC (permalink / raw)
To: netdev; +Cc: Linux Kernel
I've got something odd in a recent strace log (running on an older
kernel, I haven't yet tried to reproduce in mainline):
20418 22:06:50.583303 select(19, [7 11 12 13 14 15 16 17 18], NULL,
NULL, {0, 498508}) = 1 (in [11], left {0, 0}) <5.074137>
select() was called with a timeout of half a second. Five seconds later
it returns with zero time left and a single socket readable. Why
wouldn't it have returned after half a second with a timeout?
My immediate suspicion would be to look at scheduler behaviour, but are
there any other explanations? I'm fairly sure system time wasn't
changed during this interval (the system should have been ntp-synced).
Thanks,
Chris
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-06-23 16:00 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-06-23 16:00 looking for explanation of select() timeout behaviour Chris Friesen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).