Re: Shared Display Lists ?

New Message Reply Date view Thread view Subject view Author view

Sharon Clay (src++at++rose.asd.sgi.com)
Wed, 21 Aug 1996 11:29:42 -0700

+>---- On Aug 21, 3:39pm, Gilles Reymond wrote:
> Subject: Shared Display Lists ?
->From guest++at++holodeck.csd.sgi.com Wed Aug 21 08:14:34 1996
->Date: Wed, 21 Aug 1996 15:39:18 +0200
->From: reymond++at++corysmailserv.corys.fr (Gilles Reymond)
->To: info-performer++at++sgi.com
->Subject: Shared Display Lists ?
->
->Hi,
->
->In a multi-processed environment, the only way for the Cull app to pass Display
->Lists to the Draw app seems to use pfDisplayLists, which store a sequence of
->Performer calls exclusively.
->
->Is it possible to similarly pass specific OpenGl commands, either in a regular
->OpenGl Display List or included in the pfDisplayList ? There is nothing
->mentioned in the OpenGl docs regarding the _actual_ memory location of OGL
->display lists.
->

The pfDispList can only include pfCommands or pointers to
user callback functions - which then can of course make
OpenGL calls.

OpenGL allows display lists to be shared between two threads that
share an address space -- two forked processes don't cut it :-).
So, in current Performer, you cannot pass OpenGL display
lists between the CULL and DRAW processes.

src.

-- 
-----{-----{---++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:23 PDT

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