On Wed, Nov 08, 2006 at 05:25:00PM +0800, Yang JianJun wrote:
I choose oprofile to test gtkperf for performance profiling.
Perfect! But I notice you compiled XCB with optimization turned off.
This may not be entirely fair. :-)
I haven't test whether gdk-xcb is issuing more requests than the
Jamey Sharp wrote:
This approach isn't thread-safe, which is why XCB's API is designed to
discourage it. There may be various reasons why thread-safety doesn't
matter at these points in Gdk
Such as GDK is in no way threadsafe ;-)
http://developer.gnome.org/doc/API/2.0/gdk/gdk-Threads.html
On Thu, Nov 09, 2006 at 07:20:53PM -0500, Havoc Pennington wrote:
Jamey Sharp wrote:
This approach isn't thread-safe, which is why XCB's API is designed to
discourage it. There may be various reasons why thread-safety doesn't
matter at these points in Gdk
Such as GDK is in no way
On Wed, Nov 08, 2006 at 09:47:25AM +, Ross Burton wrote:
XNextRequest in libX11 is a pointer dereference and an increment, where
your XCBNextRequest is a round-trip.
I've mentioned in a previous mail, but just to be clear: No, it isn't a
round-trip. While this XCBNextRequest macro is
