>>>>> "JC" == Jeff Clites <[EMAIL PROTECTED]> writes:
JC> On Jan 3, 2004, at 12:26 PM, Uri Guttman wrote: >> that could be workable and might be faster. it does mean that locks >> are two step as well, user space test/set and fallback to kernel >> lock. we can do what nigel said and wrap the test/set in macros and >> use assembler to get at it on platforms that have it JC> This is probably already done inside of pthread (and Win32) JC> locking implementations--a check in userspace before a kernel JC> call. It's also important to remember that it's not a two-step JC> process most of the time, since most of the locking we are taking JC> about is likely to be uncontested (ie, the lock acquisition will JC> succeed most of the time, and no blocking will be needed). If we JC> _do_ have major lock contention in our internal locking, those JC> will be areas calling for a redesign. i meant in the coding and not necessarily at runtime. we still need to address when and where locking happens. uri -- Uri Guttman ------ [EMAIL PROTECTED] -------- http://www.stemsystems.com --Perl Consulting, Stem Development, Systems Architecture, Design and Coding- Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
