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=unavailable 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!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Niklas Holsti <niklas.holsti@tidorum.invalid>
Newsgroups: comp.lang.ada
Subject: Re: Feature suggestion: different task schedules
Date: Sat, 15 Jul 2017 22:23:45 +0300
Organization: Tidorum Ltd
Message-ID: <esv8dvFfq84U1@mid.individual.net>
References: <ok8kmo$1b1f$1@gioia.aioe.org> <okcud7$uhp$1@gioia.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net 5GaWFCcbhMYwBIypOC2onglSE4LWL7SogNdw33QboYqgLZ2TKj
Cancel-Lock: sha1:n5xtC4wY57zx9dGy9HoDLKcyGDY=
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:45.0)
 Gecko/20100101 Thunderbird/45.8.0
In-Reply-To: <okcud7$uhp$1@gioia.aioe.org>
Xref: news.eternal-september.org comp.lang.ada:47422
Date: 2017-07-15T22:23:45+03:00
List-Id: <comp.lang.ada>

On 17-07-15 14:30 , Victor Porton wrote:
> Surprisingly low response to my idea.

Possibly because your presentation of the idea is hard to understand. I 
certainly do not understand what you are proposing.

Please show some example code using the proposed mechanism, explain how 
it works, and why it is better than the current mechanisms.

> Should we have it in future Ada? (My opinion is "yes".)
>
> Victor Porton wrote:
>> I propose for Ada 2020 to add the following pragmas (and corresponding
>> aspects) for tasks and task types:
>>
>> pragma Schedule=>Thread;
>>
>> the regular task.
>>
>> pragma Schedule=>Manual;
>>
>> the task runs only when a protected entry is called and stops at the next
>> accept statement.
>>
>> This is usually the fastest mode in the case of one-core system.
>>
>> pragma Schedule=>Sometimes;
>>
>> the task run in either of two above modes (with tasks of a task type not
>> necessarily scheduled in the same way (some may be Thread and some
>> Manual)).
>>
>> The schedule mode may be chosen dependently on free CPU cores availability
>> to make it the fastest.
>>
>> pragma Schedule=>Dynamic;
>>
>> a task with this schedule may switch between Thread and Manual mode at any
>> moment of time. This is useful to use CPU cores effectively.
>>
>> What do you think?
>>


-- 
Niklas Holsti
Tidorum Ltd
niklas holsti tidorum fi
       .      @       .