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=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: Pascal Obry Newsgroups: comp.lang.ada Subject: Re: Feature suggestion: different task schedules Date: Fri, 14 Jul 2017 07:59:37 +0200 Organization: Home - http://www.obry.net Message-ID: <1500011977.2481.9.camel@obry.net> References: Reply-To: pascal@obry.net NNTP-Posting-Host: jAwp6sLi3TEa3F06gvHFcg.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Complaints-To: abuse@aioe.org X-Mailer: Evolution 3.22.6-1 X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:47410 Date: 2017-07-14T07:59:37+02:00 List-Id: Victor, > pragma Schedule=3D>Manual; >=20 > the task runs only when a protected entry is called and stops at the > next accept statement. >=20 > This is usually the fastest mode in the case of one-core system. I don't see the point. Call from the task the PO with a barrier. The task will be sleeping until waken-up by an event on this PO. Isn't this is exactly what you looking for? Don't assume you have to do optimization yourself. Most of the time the compiler and runtime does this for you and using the most efficient syscall on the target. --=20 =C2=A0 Pascal Obry /=C2=A0=C2=A0Magny Les Hameaux (78) =C2=A0 The best way to travel is by means of imagination =C2=A0=C2=A0http://www.obry.net =C2=A0 gpg --keyserver keys.gnupg.net --recv-key F949BD3B