Re: MCO Performace

New Message Reply Date view Thread view Subject view Author view

Sharon Clay (src++at++rose.asd.sgi.com)
Mon, 7 Oct 1996 13:37:02 -0700


+>---- On Oct 7, 1:23pm, Guy Russell wrote:
> Subject: Re: MCO Performace
->Hey Sharon,
->
->I thought he was talking about multiple pfPipes not graphics pipes. If so,
->does the genlock matter. I thought genlock was for multiple graphics pipes.

Yes - sorry, I didn't read quite carefully enough.
One of those days :-(

-> Also, he says he has only one graphics pipe, so would he not be better off
->using multiple pfChannels not pfPipes.

Much better!
Separate pfPipes are really intended to drive multiple graphics pipes.
There is a separate draw process for each pfPipe and these rendering processes
then have separate graphics contexts and will synchronously try to own the
graphics pipe and thrash terribly. It is fine for debuggin purposes to
force multiple pfPipes on a single pipe but your frame rate will be terribly
decreased.

For multiple viewports on a graphics pipeline your best option is multiple
pfChannels in one pfWindow. If you must have multiple windows for user-interface
reasons, you can have a single pfPipe manage multiple pfWindows.
If you do this, you will get better performance if you share the graphics
context across the multiple windows:
        pfPWinShare(pwin[i], PFWIN_SHARE_GL_CXT | PFWIN_SHARE_STATE_BIT |
                PFWIN_SHARE_GL_OBJS);
        pfAttachPWin(pwin[0], pwin[i]);

s-too-hyper-about-genlock-for-a-Monday-c.

-- 
-----{-----{---++at++   -----{----{---++at++   -----{----{---++at++   -----{----{---++at++
Sharon Rose Clay (Fischler) - Silicon Graphics, Advanced Systems Dev.
src++at++sgi.com  (415) 933 - 1002  FAX: (415) 965 - 2658  MS 8U-590
http://www.sgi.com/Technology/Performer/
-----{-----{---++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:53:43 PDT

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