RE: Draw Lockup (was Performer Woes)

New Message Reply Date view Thread view Subject view Author view

JSC-ER7 (hadi.m.tjandrasa1++at++jsc.nasa.gov)
Thu, 30 Oct 1997 14:07:15 -0600


Question:

Suppose I have an APP as follows:

        while ( RT_run )
            {
             ........
             pfSynch();
             ...........
             pfFrame();
            }

1) What is the role of pfFrame() called by the APP in scheduling of the
  CULL and DRAW processes (assuming they are on separate CPUs)?
2) Does pfFrame triggers the CULL and DRAW to wake up and run on
  the next vertical retrace? or the CULL runs immediately and the DRAW
  will run on the next vertical retrace? or else ........?

Thanks in advance for any responses,
Hadi

> ----------
> From: src++at++rose.engr.sgi.com[SMTP:src++at++rose.engr.sgi.com]
> Sent: Wednesday, October 29, 1997 9:01 PM
> To: Jean-Luc Dery; remi++at++remi.engr.sgi.com
> Cc: jan++at++archimedes.vislab.navy.mil;
> Subject: Re: Draw Lockup (was Performer Woes)
>
        (..............................................)

> when swapbuffers is called and APP will get to run. App goes to
> sleep in pfSync() to the next vertical retrace and will let draw run.
> Also, App and draw are
> woken by the kernel on vertical retrace interupt and do not use a
> semaphore
> to syncrhonize to the graphics pipeline.
> A semaphore is used if you are of pfPhase FREE_RUN however.
>
       (.......................................)

> src.
>
> --
> -----{-----{---++at++ -----{----{---++at++ -----{----{---++at++ -----{----{---++at++
> Sharon Rose Clay (Fischler) - Silicon Graphics, Advanced Systems Dev.
> src++at++sgi.com (650) 933 - 1002 FAX: (650) 965 - 2658 MS 8U-590
> -----{-----{---++at++ -----{----{---++at++ -----{----{---++at++ -----{----{---++at++
>
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
            Submissions: info-performer++at++sgi.com
        Admin. requests: info-performer-request++at++sgi.com


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:56:09 PDT

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