On 8/4/05, George Anzinger <[email protected]> wrote:
> Nishanth Aravamudan wrote:
> ~
> > Sorry, I forgot that sys_nanosleep() also always adds 1 to the request
> > (to account for this same issue, I believe, as POSIX demands no early
> > return from nanosleep() calls). There are some other locations where
> > similar
> >
> > + (t.tv_sec || t.tv_nsec)
>
> This is not the same as "always add 1". We don't do it this way just to
> have fun with C. If you change schedule_timeout() to add the 1,
> nanosleep() will need to do things differently to get the same behavior.
> (And, YES users do pass in zero sleep times.)
Fair enough. Will need to think about this more.
Thanks,
Nish
-
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: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces
- Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces
- Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces
- Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces
- Re: [PATCH] Add schedule_timeout_{interruptible,uninterruptible}{,_msecs}() interfaces
- [UPDATE PATCH] Add schedule_timeout_{intr,unintr}{,_msecs}() interfaces
- Re: [UPDATE PATCH] Add schedule_timeout_{intr,unintr}{,_msecs}() interfaces
- [PATCH] push rounding up of relative request to schedule_timeout()
- [UPDATE PATCH] push rounding up of relative request to schedule_timeout()
- Re: [UPDATE PATCH] push rounding up of relative request to schedule_timeout()
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
|
|