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-Thread: 103376,e81fd3a32a1cacd2 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newscon02.news.prodigy.net!prodigy.net!newsfeed-00.mathworks.com!nntp.TheWorld.com!not-for-mail From: Robert A Duff Newsgroups: comp.lang.ada Subject: Re: Arguments for single-mutex-exclusion on protected types (Was: Does Ada tasking profit from multi-core cpus?) Date: Mon, 26 Mar 2007 19:38:36 -0400 Organization: The World Public Access UNIX, Brookline, MA Message-ID: References: <5iGLh.26236$PF.18838@attbi_s21> NNTP-Posting-Host: shell01.theworld.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: pcls6.std.com 1174952316 11454 192.74.137.71 (26 Mar 2007 23:38:36 GMT) X-Complaints-To: abuse@TheWorld.com NNTP-Posting-Date: Mon, 26 Mar 2007 23:38:36 +0000 (UTC) User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.3 (irix) Cancel-Lock: sha1:VikgRX1Ta+dzIDHsISJ/o/z8qpE= Xref: g2news1.google.com comp.lang.ada:14646 Date: 2007-03-26T19:38:36-04:00 List-Id: "Randy Brukardt" writes: > "Jeffrey R. Carter" wrote in message > news:B0ULh.28294$PF.23764@attbi_s21... >> Randy Brukardt wrote: >> > >> > Nothing serious, but it's less than ideal: >> >> My concern was that you said it was impossible in Ada 95. It may not be >> ideal, but it doesn't seem to be impossible. > > I was thinking about a solution that doesn't clutter the cliient's view of > the library with (usually) irrelevant details (such as whether the library > is implemented with protected objects). After all, information hiding is > good! Info hiding is good, but one can't always have it, sadly. If we have human beings specifying numeric priorities of things, then we have the property that priorities only have meaning relative to other priorities. And that property implies that priorities are a global issue -- can't be neatly encapsulated. That's true whether we're talking about priority of tasks, or PO's (ceilings), or I/O events, or anything else. So I wouldn't blame this on ceilings specifically -- I'd blame on the general model (numeric priorities, set by programmers). In a non-real-time context, it's easy to make it all automatic. I haven't typed "nice" on Unix very often lately, and yet my editor responds well, even when I have a compute-bound process also running. In a real-time context, we have various partial solutions (earliest deadline first, and so forth). - Bob