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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,1ce6fddc56263182,start X-Google-Attributes: gid103376,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!postnews.google.com!w3g2000hsg.googlegroups.com!not-for-mail From: Maciej Sobczak Newsgroups: comp.lang.ada Subject: Ravenscar and run-time program parameters Date: Wed, 29 Aug 2007 00:48:23 -0700 Organization: http://groups.google.com Message-ID: <1188373703.936484.105650@w3g2000hsg.googlegroups.com> NNTP-Posting-Host: 137.138.37.241 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" X-Trace: posting.google.com 1188373704 23659 127.0.0.1 (29 Aug 2007 07:48:24 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Wed, 29 Aug 2007 07:48:24 +0000 (UTC) User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.12) Gecko/20070724 Red Hat/1.5.0.12-0.3.slc3 Firefox/1.5.0.12,gzip(gfe),gzip(gfe) Complaints-To: groups-abuse@google.com Injection-Info: w3g2000hsg.googlegroups.com; posting-host=137.138.37.241; posting-account=ps2QrAMAAAA6_jCuRt2JEIpn5Otqf_w0 Xref: g2news2.google.com comp.lang.ada:1582 Date: 2007-08-29T00:48:23-07:00 List-Id: As I understand, the Ravenscar profile forbids dynamically created tasks - all tasks have to be created at the library level. Consider a system where a (sub)set of tasks forms a task pool. Depending on the actual deployment, it might make sense to influence the size of this pool - in other words to influence the number of tasks that are started within the system. One obvious way to pass the requested number of tasks is to use program parameters. I don't see how this can be implemented within the constraint that all tasks have to be created at the library level. On the other hand, having a pool of tasks is often associated with the pattern where the set of tasks wait on a *single* job queue (or something conceptually equivalent) - and Max_Entry_Queue_Length=>1 would make such scenario more difficult to implement. I can still imagine the set of tasks having their own queues, though. How to parameterize the number of tasks in the Ravenscar-compliant system? -- Maciej Sobczak http://www.msobczak.com/