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=2.1 required=5.0 tests=BAYES_05,INVALID_DATE, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!info-ada From: contr23@NOSC-TECR ("CONTR23") Newsgroups: net.lang.ada Subject: Request for Comments : Distributed Ada Message-ID: <8603082031.AA22560@ucbvax.berkeley.edu> Date: Sat, 8-Mar-86 14:04:00 EST Article-I.D.: ucbvax.8603082031.AA22560 Posted: Sat Mar 8 14:04:00 1986 Date-Received: Sun, 9-Mar-86 09:18:20 EST Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: "CONTR23" Organization: The ARPA Internet List-Id: I am presently interested in accumulating a list of "concerns" that a software designer or implementor may want to considered in the design of an Ada Multi Processor System. My primary interest is to accumulate past experience that other people have had in developing software for distributed systems and determine if it is applicable for the Ada environment. Any insight into the area of distributed systems, however, will at least be considered. The follow list of "concerns" can be used to serve as an example: a) Program Development - Will pragmas be used to target specific sections of code to system processors?(The current Ada tasking model dictates that this should be transparent to implementors and designers) b) RTK Scheduler - How indivual vendors implement their scheduler may have dramatic effects on the application programs that they execute. It would be beneficial if some discussion or information pertaining to the scheduling algorithm be passed on the implementors. c) Will each processor have it's own RTK? d) How will communication be performed between each processor? Will benchmark data be available to determine the speed of rendezvous? How reliable is this communication? e) Size of the RTK? f) Will a debugger be available? Can it be executed on the development processor? This is by no means a complete list of questions, however, I feel that it may give you an idea of some of my concerns. An attempt will be made to categorize the list into distinct sections. If anyone has any suggestions with respect to the organization, please pass along your thoughts. I'll keep the list open for at least two months, then send out the accumulated list for review. ------------------ Jim Baldo E-Systems ECI Division P.O. Box 12248 St. Petersburg, FL 33733 813-381-2000 ext. 4586 CONTR23@NOSC-TECR ------