nanogui: Thread: THREADSAFE and NONETWORK

Hi,

short question: which effect have these two defines ?
IOW, if everything runs in one process space, but in multiple threads, I guess 
both NONETWORK and THREADSAFE are required. Why is THREADSAFE translated to 
THREADSAFE_LINUX in lock.h ?

#if THREADSAFE
#define THREADSAFE_LINUX	1	/* use linux threadsafe routines*/
#endif

And what has to be protected by the locks ?

Bye
Alex
-- 
Work: ####@####.#### - http://www.jenoptik-los.de
Home: ####@####.####                - http://www.kde.org
      ####@####.####               - http://www.neundorf.net

On Wednesday 14 December 2005 22:20, Alexander Neundorf wrote:
> Hi,
>
> short question: which effect have these two defines ?
> IOW, if everything runs in one process space, but in multiple threads, I
> guess both NONETWORK and THREADSAFE are required. Why is THREADSAFE
> translated to THREADSAFE_LINUX in lock.h ?
>
> #if THREADSAFE
> #define THREADSAFE_LINUX	1	/* use linux threadsafe routines*/
> #endif

And does it have to be a recursive mutex ? Or does a "normal" one suffice ?

Alex
-- 
Work: ####@####.#### - http://www.jenoptik-los.de
Home: ####@####.####                - http://www.kde.org
      ####@####.####               - http://www.neundorf.net

: short question: which effect have these two defines ?
: IOW, if everything runs in one process space, but in multiple threads, I
guess
: both NONETWORK and THREADSAFE are required.

Yes.  NONETWORK means LINK_APP_INTO_SERVER,
THREADSAFE is used to block threads entering GrXXX
function calls.


 Why is THREADSAFE translated to
: THREADSAFE_LINUX in lock.h ?
:
: #if THREADSAFE
: #define THREADSAFE_LINUX 1 /* use linux threadsafe routines*/
: #endif

I think it is for Linux's threads header file, which gives a
better pthreads implementation with the kernel.

Regards,

Greg

: And does it have to be a recursive mutex ? Or does a "normal" one suffice
?

I was tracing this out once, and thought that I was glad we were using
recursive (multi-entrant, couning) mutexs.  I'm not sure anyone
has guaranteed simple ones will work by following nested
procedure calls in nanox/client.c.  Note, however, that
no actual GrXXX calls are pre-empted and reentered, just
possible the routines underneath them.

Regards,

Greg