> Forgot to mention, you should use the cb_serialize lock to protect setting > the thread ID too.
The thread ID needs to be protected using 'spinlock', since that lock is held when reading it later. Or maybe cb_serialize would work, as long as thread_id is cleared after the callback returns... Actually, I think setting thread_id = 0 is required, since its purpose is to see if timer_stop is being called from the callback. _______________________________________________ ofw mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
