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=0.8 required=3.0 tests=BAYES_50,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.5-pre1 X-Received: by 2002:a05:6214:b6c:: with SMTP id ey12mr11536406qvb.48.1623536496313; Sat, 12 Jun 2021 15:21:36 -0700 (PDT) X-Received: by 2002:a25:6d02:: with SMTP id i2mr14908251ybc.309.1623536496035; Sat, 12 Jun 2021 15:21:36 -0700 (PDT) Path: eternal-september.org!reader02.eternal-september.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sat, 12 Jun 2021 15:21:35 -0700 (PDT) In-Reply-To: Injection-Info: google-groups.googlegroups.com; posting-host=174.71.119.33; posting-account=ix5KpAoAAAD9zo_4u1FxHVmn1uZn7U_d NNTP-Posting-Host: 174.71.119.33 References: <1d798609-8b73-4bc6-b74f-e435e8af8fedn@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <3b70ea2b-9783-48a3-999c-55486126ec9dn@googlegroups.com> Subject: Re: non-preemptive tasking on GNAT 2020 Windows 10 multicore AMD From: Dan Winslow Injection-Date: Sat, 12 Jun 2021 22:21:36 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader02.eternal-september.org comp.lang.ada:62207 List-Id: So, I am puzzled. Nothing I do makes any different whatsoever in how the li= ttle test program runs. Setting the scheduling police, setting the task ind= ividual priorities to Max_Priority, running as admin, setting pragma Lockin= g_Policy(Ceiling_Locking), etc. Nothing stops it from this exact output (ex= cept a slight variance in the X number) one two 24 cpu's task one died, x=3D 397682 Task two done, y=3D 1000001 ^C Kind of disheartening, and I'm not sure where to go next. I don't so much r= equire a non-preemptive scheduler, but my inability to affect any behavior = at all for teh tasking is really wierd, and seems like a bug of the underly= ing system. Anyone have any ideas? Is there some fundamental flaw in my lit= tle test program I'm missing? ,