From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on ip-172-31-74-118.ec2.internal X-Spam-Level: X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.5-pre1 Path: eternal-september.org!reader02.eternal-september.org!aioe.org!5WHqCw2XxjHb2npjM9GYbw.user.gioia.aioe.org.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: non-preemptive tasking on GNAT 2020 Windows 10 multicore AMD Date: Sat, 12 Jun 2021 18:30:36 +0200 Organization: Aioe.org NNTP Server Message-ID: References: <1d798609-8b73-4bc6-b74f-e435e8af8fedn@googlegroups.com> NNTP-Posting-Host: 5WHqCw2XxjHb2npjM9GYbw.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 X-Notice: Filtered by postfilter v. 0.9.2 Content-Language: en-US Xref: reader02.eternal-september.org comp.lang.ada:62200 List-Id: On 2021-06-12 18:05, AdaMagica wrote: > Dmitry A. Kazakov schrieb am Samstag, 12. Juni 2021 um 17:57:39 UTC+2: >> Because under Windows the default priority is in the time sharing class. >> As the name suggests such threads are preempted when the their quant >> expires. AFAIK, even a lower priority thread can preempt a higher >> priority one if both are time sharing. Time sharing priority only >> influences the duration of the quant and the chances to gain the processor. > > Hm OK. Is this compatible with the Ada RM? Unless tasks are scheduled by Ada from a single thread, it is difficult to implement without having administrative rights. I wonder if the behavior would change should the process start elevated and/or on a real time priority. Something like that could be a prerequisition for the pragma to work. One should take a look on the implementation notes... -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de