Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 26 Oct 2001 08:38:44 -0700 (PDT)
From:      <wollman@FreeBSD.org>
To:        prg51@morics.riga.post.lv, wollman@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject:   Re: i386/31504: nanosleep() strange behavior
Message-ID:  <200110261538.f9QFciA10760@freefall.freebsd.org>

index | next in thread | raw e-mail

Synopsis: nanosleep() strange behavior

State-Changed-From-To: open->closed
State-Changed-By: wollman
State-Changed-When: Fri Oct 26 08:21:00 PDT 2001
State-Changed-Why: 
As PHK explained, the granularity of nanosleep() is tied to the
frequency of clock interrupts, and this is not likely to change.  POSIX
says clearly:

# The suspension time may be longer than requested because the argument
# value is rounded up to an integer multiple of the sleep resolution or
# because of the scheduling of other activity by the system.

There is no portable mechanism to determine the precise value of the
sleep resolution.  The Rationale suggests that it should be less than one
second, but I can find no normative text even defining the term.

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=31504

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message



help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200110261538.f9QFciA10760>