On Mon, Jun 13, 2005 at 05:29:37PM +0100, David Woodhouse wrote:
> On Mon, 2005-06-13 at 09:10 -0700, Ulrich Drepper wrote:
> > poll()'s timeout value is measrued in milliseconds. Using a 32bit
> > value, as implied by using 'int' for the type, limits the mximum
> > timeout to be 2^31-1 milliseconds, which means about 24 days.
>
> Ah, OK. I thought you were talking about the timespec in pselect(),
> because that's what you quoted.
>
> Yes, we should make the time for ppoll() a 64-bit value, so you can
> request a time period longer than 24 days. Shall we also switch to
> microseconds?
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.
Jakub
-
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/
- References:
- Re: Add pselect, ppoll system calls.
- Re: Add pselect, ppoll system calls.
- Re: Add pselect, ppoll system calls.
- Re: Add pselect, ppoll system calls.
- Re: Add pselect, ppoll system calls.
- Re: Add pselect, ppoll system calls.
- Re: Add pselect, ppoll system calls.
- Re: Add pselect, ppoll system calls.
- Re: Add pselect, ppoll system calls.
- Re: Add pselect, ppoll system calls.
[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]