> I think passing const struct timeval * or const struct timespec *
> (depending if you want micro or nanoseconds) is better and what
> other functions use for timeouts, then passing int64_t.
If we can design ppoll() any way we like, which seems likely, I would
prefer having the timeout given as an absolute timestamp. It would
save some gettimeofday() (or clock_gettime()) syscalls and simplify
user code in common cases.
If I'm not mistaken, sem_timedwait() and pthread_cond_timedwait() were
designed to take an absolute timeout for this reason.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
