RE: Penalty of calling a protected operation or task-entry.

["Beard, Frank Randolph CIV" <frank.beard@navy.mil>]

-----Original Message-----
From: tmoran@acm.org 

>> As I have understood there is a time-penalty when calling a protected
>> operation or task-entry. Im thinking about adminstrative cost
>   Have you profiled your program and found that the protected
> operations are the bottleneck?

>> Is there some approach to remove penalty from the "read" operation?
>   If another task is doing a Write, then Read will have to suffer the
> penalty of waiting.  If not, then it depends on how efficient is your
> particular system's implementation.

To add to what Tom said, we've never had the task-entry rendezvous
become enough of a time-penalty to cause us any problems.  Protected
types were partially created/implemented to alleviate the "penalty"
of the rendezvous.  So use a protected type if it fits your design.

Besides, what's your alternative if you need protected operations.
Protected types are at least as fast, or faster, than going to an
OS level semaphore.

Frank