> >From recent input on this list it is clear that the > current threadsafe_lock()/unlock() functions don't cut it. > We will need to work out how these functions should look. threadsafe_lock()/unlock() as a name is misleading. sharing memory between processes, requiring locking, is nothing to do with threads.
there may be some code / techniques in samba that may be worth examining: this is not at all dis-similar to file locking, except it happens to be memory, not files. ... so they're shared, mmap'd, threaded, so what? it's all the same... :) lukes
