How can the glibc do things like that? :
> > #define posix_bump_timer(timr) do { \
> > (timr)->it_timer.expires += (timr)->it_incr; \
> > - (timr)->it_overrun++; \
> > + if ((timr)->it_overrun < DELAYTIMER_MAX)\
> > + (timr)->it_overrun++; \
> > }while (0)
In addition knowing that DELAYTIMER_MAX is dependant on the
implementation and that the implementation is now in the kernel I think
DELAYTIMER_MAX should be defined by the kernel. Then glibc can do its
usual trick of stealing all the constant from the kernel...
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/