Browse Prior Art Database

Remote Procedure Calls for an Attached Processor

IP.com Disclosure Number: IPCOM000108746D
Original Publication Date: 1992-Jun-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 2 page(s) / 80K

Publishing Venue

IBM

Related People

Johnson, MA: AUTHOR

Abstract

An implementation of remote procedure calls (RPC) for managing communication between a main processor and an attached processor allows transparent execution of user code on the attached processor. A language for specifying the interface between the two processors and an RPC stub generator automate the processor for creating the interface between the two processors.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Remote Procedure Calls for an Attached Processor

       An implementation of remote procedure calls (RPC) for
managing communication between a main processor and an attached
processor allows transparent execution of user code on the attached
processor.  A language for specifying the interface between the two
processors and an RPC stub generator automate the processor for
creating the interface between the two processors.

      The concept of a RPC normally applies to a networked
environment.  Specializing the RPC protocol to a non-networked
environment, such a one having a main processor and an attached
processor, requires no information in addition to the arguments of
the called subroutine, making the interface completely transparent to
the application program.  An interface connecting the main processor
and the attached processor manages the communication between the two
processors.  An RPC stub generator translates an interface
specification into subroutines that implement the communication
between the processors and invoke the desired subroutine on the
attached processor.

      Fig. 1 shows User Subroutine 1 calling User Subroutine 2 in the
original program that runs entirely on the main processor.  Fig. 2
shows the same user subroutines, except that User Subroutine 2 is
running on the attached processor. Instead of calling User Subroutine
2 directly, User Subroutine 1 calls the RPC stub.  The RPC stub runs
on the main processor and communicates with the RPC dispatcher that
is running on the attached processor.  Some communication method,
such as named pipes, connects the two processors. After receiving the...