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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,a5681531ca1cf09e X-Google-Attributes: gid103376,public From: kilgallen@eisner.decus.org (Larry Kilgallen) Subject: Re: Tasking performance between Ada83 and Ada95 Date: 1997/06/23 Message-ID: <1997Jun23.101735.1@eisner>#1/1 X-Deja-AN: 252023819 X-Nntp-Posting-Host: eisner.decus.org References: <1997Jun6.115223.7384@relay.nswc.navy.mil> <7h6UFCAdNsmzEwg3@walsh.demon.co.uk> <5oir0v$mgu$1@gonzo.sun3.iaf.nl> X-Nntp-Posting-User: KILGALLEN X-Trace: 867075466/29382 Organization: LJK Software Newsgroups: comp.lang.ada Date: 1997-06-23T00:00:00+00:00 List-Id: In article <5oir0v$mgu$1@gonzo.sun3.iaf.nl>, Geert Bosch writes: > IMO the best solution would be to start X system level threads and > implement a user-level threads package on top of it. Of course > there will be a little extra need for locking, but on platforms > suitable for multi-processing there exist CPU-instructions that > make the implementation of fast locks possible. That is the method used by Alpha VMS. The kernel thread primitives in fact are not documented for public consumption. The documented interface is the DECthreads library (which has a couple different APIs matching varying styles and standards). DECthreads creates the user-mode lightweight threads which then get scheduled onto some number of kernel threads (typically numbering on the order of the number of CPUs). Larry Kilgallen