[575] in The GTK GIMP ToolKit mailing list archive

home help back first fref pref prev next nref lref last post

[gtk-list] Re: Making gtk thread-safe

daemon@ATHENA.MIT.EDU (Erik Troan)
Tue Jul 29 17:43:42 1997

Date: Tue, 29 Jul 1997 17:43:04 -0400 (EDT)
From: Erik Troan <ewt@redhat.com>
To: gtk-list@redhat.com
In-Reply-To: <Pine.LNX.3.95.970729171648.3555A-100000@dilbert.redhat.com>
Resent-From: gtk-list@redhat.com
Reply-To: gtk-list@redhat.com

On Tue, 29 Jul 1997, Elliot Lee wrote:

> I've been thinking about making gtk thread safe. It seems like it is
> becoming an often-requested feature. Here are some random thoughts of mine
> on the issue: 
> 
> The easiest way to do this is the global mutex. This doesn't help
> performance very much, though.

I wonder where gtk spends most of its time? It seems pretty efficient, so
I'd *guess* that the real time sinks are in Xlib and the Xserver. If that's
the case, a single mutex is all you need. 

Also, most multithreaded windowing apps dedicate a single thread to the
user interface, which would also suggest this approach. I suspect that
any type of fine-grained locking on gtk would be a huge loss?

Erik

-------------------------------------------------------------------------------
| "Tarball is idiomatically related to furball and hairball" -- Carl D. Roth  |
|                                                                             |
|       Erik Troan   =   ewt@redhat.com     =    ewt@sunsite.unc.edu          |

--
To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null


home help back first fref pref prev next nref lref last post