public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Piel <Eric.Piel@Bull.Net>
To: Ulrich Drepper <drepper@redhat.com>
Cc: george anzinger <george@mvista.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: DELAYTIMER_MAX is defined
Date: Wed, 07 May 2003 14:00:12 +0200	[thread overview]
Message-ID: <3EB8F54C.CC5488F0@Bull.Net> (raw)
In-Reply-To: 3EB8BA67.4060708@redhat.com

Ulrich Drepper wrote:
> This is not correct.  The constant does not have to be defined.  Like
> all the various *_MAX constants they only have to be defined if there is
> a fixed limit the implementation has.  If there is none or it can only
> be defined dynamically at runtime the the macro must not be defined.
> Instead sysconf() can provide the value.  But not even this is
> necessary.  sysconf() can return -1.
Sorry, I wasn't aware about this POSIX rule, thank you for pointing out
this. Knowing that it would obviously be better providing support of the
constant _SC_DELAYTIMER_MAX for sysconf() and return a value. 

This would imply there is now some job for glibc. However it's still
unclear for me how the glibc would know about wich value it should 
return while this question would be so easy to answer for the kernel!
Also AFAIK, right now, only the NPTL supports the new syscalls for the
timers (and none supports the clocks syscalls). Does it mean a special
__sysconf() is necessary in the NPTL? Well, probably that's why you 
suggested -1 as a return value I guess :-) 

> 
> Anyway, in this specific case the implementation should be protected
> against the ever so improbable overflow of the counter, yes.  If you
> want a fixed value, fine.  If you want to use ULONG_MAX (or whatever),
> good too.  Whether we advertise this limit is another thing.
> Advertising it in the macro means it never can be changed.
> 
You are right also here, of course with this point of view it's
better not putting any constant.
So the patch could become something like that: ?

diff -ur linux-2.5.67-ia64-hrtcore/include/linux/posix-timers.h linux-2.5.67-ia64-hrtimers/include/linux/posix-timers.h
--- linux-2.5.67-ia64-hrtcore/include/linux/posix-timers.h      2003-04-22 11:10:44.000000000 +0200
+++ linux-2.5.67-ia64-hrtimers/include/linux/posix-timers.h     2003-05-06 16:07:56.000000000 +0200
@@ -25,6 +59,7 @@
 
 #define posix_bump_timer(timr) do { \
                         (timr)->it_timer.expires += (timr)->it_incr; \
-                        (timr)->it_overrun++;               \
+                        if ((timr)->it_overrun < INT_MAX)\
+                            (timr)->it_overrun++;               \
                        }while (0)
 #endif

Eric

  reply	other threads:[~2003-05-07 11:48 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
2003-05-07  7:48     ` Ulrich Drepper
2003-05-07 12:00       ` Eric Piel [this message]
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=3EB8F54C.CC5488F0@Bull.Net \
    --to=eric.piel@bull.net \
    --cc=drepper@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox