Messages in this thread | | | Date | Mon, 13 Dec 1999 15:38:11 +0100 | From | Jamie Lokier <> | Subject | Re: gettimeofday() a special case : why? |
| |
David S. Miller wrote: > Well, first of all, every single network packet which arrives at or > leaves your system uses the guts of gettimeofday() to timestamp > the packet.
That has nothing to do with optimising the syscall path, or avoiding the kernel/user transition.
Optimising user-space gettimeofday() is worth a little attention because a lot of select-loop based apps call it before and after each select().
Any program that's doing lots of calculations with a timer-driven progress meter may also use it. Though timer signals can be used instead.
Select loops also often do signal mask things -- are they worth the same attention as gettimeofday()?
-- Jamie
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |