On Fri Nov 19 2010 at 00:11:12 +0000, Andrew Doran wrote: > You can release it with either call, mutex_spin_ is just a way to avoid > additional atomic operations. The ususal case is adaptive mutex, but > stuff like the dispatcher/scheduler makes use of spin mutexes exclusively > and the fast path versions were invented for that. (Because you can measure > the effect with benchmarks :-).
Speaking of which, something I (and a few others) have been thinking about is to have constantly running benchmarks (akin to constantly running tests). That way we can have a rough idea which way performance and resource consumption is going and if there are any sharp regressions. Are your old benchmarking programs still available somewhere?
