Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!apple!csibtfr!excelan!leadsv!practic!vine!ksh
From: ksh@vine.VINE.COM (Kent S. Harris)
Newsgroups: comp.realtime
Subject: Re: Shared memory with multiple processors running VxWorks
Keywords: VxWorks/multiple processors/ shared memory
Message-ID: <3439@vine.VINE.COM>
Date: 11 Sep 89 15:26:20 GMT
References: <4252@ncar.ucar.edu> <311@zip.eecs.umich.edu>
Reply-To: ksh@vine.UUCP (Kent S. Harris)
Organization: Vine Technology, Cupertino, CA
Lines: 10

I have had as many as 11 processors communicating across a VME bus under
pSOS.  At the lowest level the communication model was one of shared
memory.  The application interface was a complete device driver in the
usual pSOS sense which included an exclusion exchange (special message)
and a synchronization exchange for supervisor and Interrupt Service
Routine (ISP) synchronization.  To keep life simple, I did not implement
packet fragmenting so applications where limited on the size of the
message they could send, but this would be simple to do.  I did implement
a stream style interface as an application library so an application could
do byte stream i/o.  All in all, no big ditty.