On Wed, 2004-07-07 at 16:00, Alan Stern wrote: > > Arrgh! You know, this was a possibility that occurred to me while writing > this code, but then I forgot and never checked up on it. > > The problem is that rw-semaphores don't have the semantics I need. I need > something where, if the semaphore is locked for reading and a writer is > waiting for the lock, another reader will be granted a readlock > immediately. But that's not how it works; another reader will be forced > to wait until the writer is done. > > Okay, guess I'll have to do a little roll-your-own. Try out this patch. > It assumes you have already applied that 1-liner.
Everything is working properly now. Jesse -- Jesse Stockall <[EMAIL PROTECTED]> ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
