Date: Wed, 05 Aug 1998 17:53:29 +0930 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: John Birrell <jb@cimlogic.com.au> Cc: doconnor@gsoft.com.au (Daniel O'Connor), stevel@mail.cdsnet.net, tlambert@primenet.com, hackers@FreeBSD.ORG Subject: Re: Threaded X libs.. Message-ID: <199808050823.RAA15967@cain.gsoft.com.au> In-Reply-To: Your message of "Wed, 05 Aug 1998 18:13:13 %2B1000." <199808050813.SAA27521@cimlogic.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> -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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808050823.RAA15967>