Re: Is Volumizer thread safe

New Message Reply Date view Thread view Subject view Author view

even.andersen@oslo.pgs.com
Mon, 26 Apr 99 09:51:28 +0100

Thank you to those that replied,
I have some more questions.

I asked:
> ...
> I have a core dump in voAppearanceActions::texgenSetEquation.
> ...
> voAppearanceActions::texgenSetEquation((voBrick*)0x10224c10)
> ...
> voAppearanceActions::texgenSetEquation((voBrick*)0x1022c290)
> ...

rg@hoek.engr.sgi.com
> ...
> Volumizer is not thread safe.
> ...
> You can still, however, use Volumizer in a multi-threaded environment. For
> example, consult Chikai Ohazama's monster examples (sproc based) distributed
> with Volumizer 1.1 (freezing later today). If you want to multi-tread your
> own application, in most cases you just need to identify the critical sections
> and put suitable locking in.

Can I download Volumizer 1.1 somewhere (Currently I have 1.0)
If texgenSetEquation does not work, I believe this indicates Volumizer
1.0
is not reentrant either.

I can ofcourse lock each call to volumizer, but I was hoping someone has
more specific info as to wich calls have to be locked.

At the very least it seems like I must provide texturing
(as opposed to let volumizer handle texture objects, texture
coordinates,
 etc., ...)

> One thing you cannot do in OpenGL is to have more than one thread attached to
> the same graphics context (i.e., two treads cannot call glTexGendv()). And
> even if you could, it would not speed things up. What are you attempting to
> do?

I'm working on a mpu based program (MPU ver. 1.1), and I am drawing to
two
pipes at the same time. The sample program allocates a copy of the data
for
each process. (BTW, I'm using sproc(, PR_SALL, )).

Even Oscar Andersen

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Nov 01 1999 - 12:06:41 PST