Re: [patch v2 0/5] Nano/Microsecond resolution for select() and poll()
- From: Willy Tarreau <w@xxxxxx>
- Date: Sun, 31 Aug 2008 18:55:54 +0200
Hi Arjan,
On Sun, Aug 31, 2008 at 09:28:28AM -0700, Arjan van de Ven wrote:
One thing to note is that on my machine, the current select() implementation
will return after 1997 microseconds when asked for 1999 microseconds; this
can be seen in a zoom in of the graph above:
http://www.tglx.de/~arjan/zoom.png
E.g. select() is returning too early in current Linux kernels; and this is
also fixed (by nature) by this patch series.
This is a good news. I've been bothered by this problem for a long time
and got used to add 99999 us to any delay fed to select() (that started
when HZ=100). I remember having noticed performance improvements in my
applications using this trick even on other systems, so I don't think
that Linux is the only one with this anomaly. I think it's simply caused
by the rounding methods which make it hard to compute an accurate deadline
when a value is converted before being added to jiffies.
I do not remember noticing this on epoll though. Maybe it's just because
I did not look close enough :-/
Cheers,
Willy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- [patch v2 0/5] Nano/Microsecond resolution for select() and poll()
- From: Arjan van de Ven
- [patch v2 0/5] Nano/Microsecond resolution for select() and poll()
- Prev by Date: Re: MTD/block regression (was Re: Slub debugging NAND error in 2.6.25.10.atmel.2)
- Next by Date: Re: ksoftirqd high cpu load on kernels 2.6.24 to 2.6.27-rc1-mm1
- Previous by thread: [PATCH 5/5] select: switch select() and poll() over to hrtimers
- Next by thread: Re: [patch v2 0/5] Nano/Microsecond resolution for select() and poll()
- Index(es):