From owner-freebsd-hackers Wed Aug 5 01:24:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09195 for freebsd-hackers-outgoing; Wed, 5 Aug 1998 01:24:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09189 for ; Wed, 5 Aug 1998 01:24:08 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id RAA15967; Wed, 5 Aug 1998 17:53:29 +0930 (CST) Message-Id: <199808050823.RAA15967@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: John Birrell cc: doconnor@gsoft.com.au (Daniel O'Connor), stevel@mail.cdsnet.net, tlambert@primenet.com, hackers@FreeBSD.ORG Subject: Re: Threaded X libs.. In-reply-to: Your message of "Wed, 05 Aug 1998 18:13:13 +1000." <199808050813.SAA27521@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Aug 1998 17:53:29 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -pthread was added to gcc first in -current, then to -stable after the > release of 2.2.6. All it does is to use libc_r instead of libc. Linking > with -lc_r, but no -nostdlib means that you risk getting functions from > libc if the symbols aren't in libc_r. The only one that comes to mind > is poll(). If XFree86 uses poll() instead of select(), you can expect to > have problems. Ahh.. thanks for the tip :) I'm glad I found that out _now_ rather than some handfuls of hair later ;) > It's been a while since I looked at XFree86 thread code, but I remember > something about a single socket to the connected display, with no way > to have a connection per dialog. You lose some of the benefits of > threading by having a single socket. It depends on your application, > but I don't like mine performing at the speed of X. I always code > the X calls in the initial thread and let all the background threads > buffer commands for it that are processed as soon as it can. YMMV. Yes, basically the 'threaded' Xlibs are just normal Xlibs with the ability to lock a display, so aren't teribbly much use. Still, you would probably gain performance if you used one thread per display(not that that situation would present it self very often..) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message