From: Eric Piel <Eric.Piel@Bull.Net>
To: george anzinger <george@mvista.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: DELAYTIMER_MAX is defined
Date: Wed, 07 May 2003 09:29:46 +0200 [thread overview]
Message-ID: <3EB8B5EA.BD5D1C19@Bull.Net> (raw)
In-Reply-To: 3EB81719.3050705@mvista.com
george anzinger wrote:
>
> Eric Piel wrote:
> > Playing around with the posix timers I've noticed that DELAYTIMER_MAX is
> > not defined. This constant is specified in the POSIX specifications. It
> > should contain the maximum possible value of overruns on a signal. It is
> > also said that the overrun shouldn't overflow. cf
> > http://www.opengroup.org/onlinepubs/007904975/functions/timer_getoverrun.html
> >
> > So here is a patch to add this constant and a check that the overrun
> > variable never overflow. It's for 2.5.67 but should apply flawlessly to
> > 2.5.69 too.
> I think this is needed in glibc. I am not sure how that relates to
> kernel defines.
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
next prev parent reply other threads:[~2003-05-07 7:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 16:33 [PATCH]: DELAYTIMER_MAX is defined Eric Piel
2003-05-06 20:12 ` george anzinger
2003-05-07 7:29 ` Eric Piel [this message]
2003-05-07 7:48 ` Ulrich Drepper
2003-05-07 12:00 ` Eric Piel
2003-05-07 15:02 ` george anzinger
2003-05-07 18:21 ` Ulrich Drepper
2003-05-07 18:47 ` george anzinger
2003-05-07 19:03 ` Ulrich Drepper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EB8B5EA.BD5D1C19@Bull.Net \
--to=eric.piel@bull.net \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.