A spurious wakeup is MUCH better than a lost wakeup, as you point out the recovery method for spurious wakeups.
-derek "Srikanth Vishwanathan" <[EMAIL PROTECTED]> writes: > > i know it would leak, but that didnt concern me a great deal. at > > shutdown you can just go through the hash table and free the memory. > > the addition of afs_addevent() makes the behavior of the event code > > slightly different from other platforms. is that bad? i dont know. > > If afs_getevent() returns NULL, sleep will return prematurely. But this > is no different from a spurious wakeup. The caller makes sure that sleep > is called in a "while(condition not satisfied) sleep" loop that takes > care of this. > > > _______________________________________________ > OpenAFS-devel mailing list > [EMAIL PROTECTED] > https://lists.openafs.org/mailman/listinfo/openafs-devel -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH [EMAIL PROTECTED] PGP key available _______________________________________________ OpenAFS-devel mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-devel
