From owner-freebsd-current  Tue May 14 20:40:41 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id UAA10361
          for current-outgoing; Tue, 14 May 1996 20:40:41 -0700 (PDT)
Received: from bunyip.cc.uq.oz.au (pp@bunyip.cc.uq.oz.au [130.102.2.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA10353
          for <current@freebsd.org>; Tue, 14 May 1996 20:40:33 -0700 (PDT)
Received: from bunyip.cc.uq.oz.au by bunyip.cc.uq.oz.au 
          id <13737-0@bunyip.cc.uq.oz.au>; Wed, 15 May 1996 13:15:02 +1000
Received: from netfl15a.devetir.qld.gov.au 
          by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP 
          id NAA20321; Wed, 15 May 1996 13:15:30 +1000
Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) 
          id DAA17180; Wed, 15 May 1996 03:15:06 GMT
Message-Id: <199605150315.DAA17180@netfl15a.devetir.qld.gov.au>
X-Mailer: exmh version 1.6.5 12/11/95
To: John Birrell <cimaxp1!jb@melb.werple.net.au>
cc: beta@xfree86.org, current@freebsd.org
Subject: Re: libc_r threads doco?
In-reply-to: Your message of "Wed, 15 May 1996 12:17:29 +1000." <199605150216.MAA10709@melb.werple.net.au>
X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 
        7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! 
        >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 
        M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 15 May 1996 13:15:04 +1000
From: Stephen Hocking <sysseh@devetir.qld.gov.au>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


> 
> We looked at the threaded X11R6 code and decided that it really wasn't
> much use because all that it does for you is lock the one connection 
> to the server (from XOpenDisplay) and then the thread that has the lock
> has to consume all events. This doesn't allow a programmer to create
> a thread to drive each dialog (which is what we wanted to do).
> 
> To use the libc_r stuff with X11R6 shouldn't be a big deal. I haven't
> actually done it (we just use the FreeBSD libs off the WC CDs and ensure
> that only the initial thread accesses X), but there is a POSIX thread
> option somewhere in X's config files. Set that and make sure you
> compile X with -D_THREAD_SAFE.
> 

Aaah. OK then, pity about that. At one stage they had a threaded X server in 
the workInProgress directory, but there's been no work on that for some time 
as far as I know. It would've been good, as one could run say the font 
renderer as a separate thread (or group of threads) and still be able to get 
some parallelism. You can sort-of get that by using a font server but it's not 
the same.


-- 
The views expressed above are not those of the Worker's Compensation Board of
Queensland, Australia.