From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,d3ac444cc1efa302 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-09-25 12:30:45 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!wn14feed!wn13feed!wn11feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!sccrnsc03.POSTED!not-for-mail From: tmoran@acm.org Newsgroups: comp.lang.ada Subject: Re: Penalty of calling a protected operation or task-entry. References: <8cGcb.25659$os2.355577@news2.e.nsc.no> X-Newsreader: Tom's custom newsreader Message-ID: NNTP-Posting-Host: 12.234.124.41 X-Complaints-To: abuse@comcast.net X-Trace: sccrnsc03 1064518244 12.234.124.41 (Thu, 25 Sep 2003 19:30:44 GMT) NNTP-Posting-Date: Thu, 25 Sep 2003 19:30:44 GMT Organization: Comcast Online Date: Thu, 25 Sep 2003 19:30:44 GMT Xref: archiver1.google.com comp.lang.ada:42924 Date: 2003-09-25T19:30:44+00:00 List-Id: >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.