Re: nanosleep & sginap

New Message Reply Date view Thread view Subject view Author view

Phil Keslin (philk++at++cthulhu.engr.sgi.com)
Thu, 01 Apr 1999 09:47:26 -0800

Mattias.Johansson++at++saab.se wrote:
>
> Somebody forgot to update the manuals... or tell me about it, though :-)
> >From the manual:
>
> Note that if the calling thread is interrupted by a signal before the
> specified number of ticks has elapsed, sginap will return
> prematurely.

This is still true (and I believe true for some sleeps as well).
Although it is possible for the sginap to awaken due to a signal, there
are no signals delivered to the DRAW process that would have this
effect. Even if it did, the wakeup would be effective only if it occured
in the frame just prior to the vertical retrace in which the swapbuffers
should happen. If it doesn't, then the DRAW will simply call sginap
again.

- Phil

-- 
Phil Keslin <philk++at++engr.sgi.com>

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Thu Apr 01 1999 - 09:47:30 PST

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.