Re: Implementation Locks

[Jeffrey Carter <spam.jrcarter.not@spam.not.acm.org>]

On 02/15/2014 01:20 PM, sbelmont700@gmail.com wrote:
>
> Now in Ada, I have difficulty giving up the habit and lay awake at night
> worrying about whether the implementation is going busy-wait or block for a
> protected action or closed entry, especially now that everyone has multicore
> CPU's.  I'm particularly consternated by closed entries, since I doubt the
> compiler can predict whether it will open back up in several microseconds or
> in several days.  Is it unreasonable to expect an implementation to use some
> sort of dynamic, hybrid model that takes into account both how many CPU's are
> in the system and the average time to wait?  Should I just trust the runtime
> and try not to worry?  Is there even anything I can do about it either way?

You should trust the implementation, and measure your results. If you're meeting 
your timing requirements, then you have nothing to worry about.

-- 
Jeff Carter
"In the frozen land of Nador they were forced to
eat Robin's minstrels, and there was much rejoicing."
Monty Python & the Holy Grail
70