On Fri, 2011-02-04 at 16:42 +0200, Rami Ylimäki wrote: > This change makes it possible to detect missing XInitThreads calls in > X clients. If a client hasn't called XInitThreads and enters a > critical section in Xlib concurrently, the client will be aborted with > a message informing about the missing call. > > Enabling thread safety by default causes a minor performance > regression for single threaded X clients. However, the performance > regression is only noticeable in the worst case situation. In > realistic use cases the overhead from unnecessary locking is difficult > to see. > > Relative x11perf results showing the amount of regression for worst > case and some common operations are shown below. > > unlocked/locked Operation > ----------------- ------------------------------------ > 1.001 500-pixel line > 1.000 Copy 500x500 from window to window > 2.609 X protocol NoOperation > > Signed-off-by: Rami Ylimäki <[email protected]> > Reviewed-by: Erkki Seppälä <[email protected]> >
For the configuration part, Reviewed-by: Gaetan Nadon <[email protected]>
signature.asc
Description: This is a digitally signed message part
_______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
