On Tue, Feb 24, 2009 at 8:57 AM, Aaron Knister <[email protected]> wrote: > Yeah the code uses lock a fair bit. As I understand it the primary use of > lock in this application is around an instruction tree to be processed.
Then it's possible that the time spent in futex() is due to one of two things: 1. A poor implementation of futex(). 2. Time spent blocking waiting for another thread to release its lock. This will look on a profiler like this function is taking forever to return, because it will not return until the lock is available. -- Chris Howie http://www.chrishowie.com http://en.wikipedia.org/wiki/User:Crazycomputers _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
