Browse Prior Art Database

Remote Procedure Call Extensions for Multiprocessors

IP.com Disclosure Number: IPCOM000114272D
Original Publication Date: 1994-Dec-01
Included in the Prior Art Database: 2005-Mar-28
Document File: 2 page(s) / 66K

Publishing Venue

IBM

Related People

Jindal, A: AUTHOR

Abstract

Disclosed is a mechanism to recognize and use multiprocessor configuration for fast execution of Remote Procedure Calls (RPCs). The extensions have been added to DCE-RPC Runtime component to use multiprocessor configuration to enable fast execution of RPCs among client(s) and server(s) executing on the same multiprocessor.

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

Remote Procedure Call Extensions for Multiprocessors

      Disclosed is a mechanism to recognize and use multiprocessor
configuration for fast execution of Remote Procedure Calls (RPCs).
The extensions have been added to DCE-RPC Runtime component to use
multiprocessor configuration to enable fast execution of RPCs among
client(s) and server(s) executing on the same multiprocessor.

      The extension to the Distributed Computing Environment (DCE)
RPC Runtime component is totally transparent to the DCE application
developer.  The extended RPC runtime:  a) enables processes of a
distributed application executing on the same multiprocessor to
communicate via message queues,  b) enables processes executing on a
multiprocessor to communicate with processes executing on other
machines on the network via internet domain sockets.

EXTENDED RPC MODEL
  1.  RPC Runtime Initialization: The RPC runtime performs the
       following steps during its initialization:
      a.  It creates a data structure called the cluster_host list,
           and populates it with network addresses associated with
           each processor of a multiprocessor.
       b.  It creates a message queue during internet domain socket
           creation.  The host network address of each processor of a
           multiprocessor, and the port number (obtained during
internet
           domain socket creation) is used as a key for creating the
           message queue.  This queue is used to receive messages
           (destined for this process) from processes executing on
other
           processors of a multiprocessor.  The communicating
processes
           on a multiprocessor already know about other process's
           network address and port number, thereby eliminating the
need
           to exchange message queue ids.
       c.  It registers the created queue with an automatic queue
           purging facility.  The system V messa...