Re: Performer within Multi-threaded Applications

New Message Reply Date view Thread view Subject view Author view

Rémi Arnaud (remi++at++remi.asd.sgi.com)
Sun, 11 May 1997 09:50:58 -0700 (PDT)


David Higginbotham wrote:
>
> We have an large multi-threaded application that gathers and computes
> data for a shipboard combat system. This program is divided into several
> threads such as real-time data gathering, simulation, display, etc.
>
> Right now the display thread is implemented using OpenGL. Our app has
> ability to use either sproc() or Posix threads, selectable at compile
> time. In either case global memory is automatically shared among all
> threads - the Unix brand of shared memory is not used.
>
> We would like to use Performer to implement the display thread. The
> question is, what complications can arise by generating a Performer
> application as a thread in a larger system? Will this interfere with
> Performer's multi-processing and shared memory? Any advice on the best
> way to do such an integration?
>

 Performer pfConfig() call creates fork() processes based on the MP
 model asked by pfMultiprocess() call.
 It is very hard to call fork from a pthread, but it should be not a
 problem is you do the sproc/pthread after pfConfig() in the APP
 process created by Performer. Using pthread should not prevent
 you to use the Arena (shared memory) that performer creates
 to enable inter-process communication within Performer.

    _ / _ _
|_) _ ._ _ o /\ |_)|\ | /\ | || \
| \(/_| | || /--\| \| \|/--\|_||_/
                                           
=======================================================================
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:55:12 PDT

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