Interprocess communications system and method utilizing shared memory for message transfer and datagram sockets for message control

• US 5,652,885 A
• Filed: 05/25/1993
• Issued: 07/29/1997
• Est. Priority Date: 05/25/1993
• Status: Expired due to Term

• Current Assignee: Storage Technology Corp (Oracle Corporation)
• Original Assignee: Storage Technology Corp (Oracle Corporation)
• Inventors: Trachy, David L., Reed, Dennis F., Montgomery, James W.
• Primary Examiner(s): Kriess, Kevin A.
• Application Number:
  US08/066,213
• Time in Patent Office: 1,526 Days
• Field of Search: 395/650, 395/700
• US Class Current: 713/1
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 69/326 in the transport layer [OSI layer 4] H04L69/16 takes precedence
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

The present invention is an interprocess communications (IPC) system and method which utilizes shared memory to transfer message contents and a separate, efficient notification mechanism to perform message control functions. The present invention supports robust, asynchronous communications between potentially large number of software application processes residing on any single or tightly-coupled multiple processor arrangement supporting shared memory between the processes. The present invention is a combination of existing IPC mechanisms available in most commercially available UNIX operating systems. The IPC mechanism utilizes the presently available UNIX shared memory IPC mechanism for transferring message contents and the presently available UNIX datagram socket IPC mechanism for message control and notification. The IPC mechanism may be adapted to other operating system environments. The IPC mechanism performs a controlled shutdown of the interprocess communications associated with a user process which has ceased executing. The shared memory allocated for the IPC mechanism is periodically audited to reclaim lost shared memory blocks due to user process failures.

Claims

1. An interprocess communications system for transferring message data from a source user process to at least one destination user process in a computer-based system providing a Unix operating system environment and a shared memory, the interprocess communications system comprising:

initialization means for creating and initializing a shared memory segment in the shared memory, said shared memory segment including a plurality of message blocks having a preamble portion and a message content portion, said preamble portion having an availability status region, a time allocation region, and an identification region;

sending means for placing the message in one of said plurality of message blocks and for placing a shared memory block index in a datagram socket interprocessor communications mechanism associated with the destination user process, said shared memory block index identifying said one of said plurality of message blocks which contain the message data;

receiving means for receiving said shared memory block index from said datagram socket interprocessor communications mechanism and for using said shared memory block index for retrieving the message data from said one of said plurality of message blocks;

maintenance means for maintaining the availability of said plurality of message blocks in said shared memory segment, said maintenance means periodically reading said time allocation region and comparing the time in said time allocation region with a predetermined value; and

shutdown means for performing a controlled shutdown of the interprocessor communications system when the source user process ceases execution, said shutdown means guaranteeing that any messages associated with the source user process are sent to the at least one destination user process before the source user process is terminated.

2. The system of claim 1, wherein said sending means comprises:

first memory allocation means for allocating said one of said plurality of message blocks;

first message transfer means for transferring the message from a local memory location associated with the source user process to said allocated message block, and for placing the message in a temporary buffer when said first memory allocation means cannot allocate said one of said plurality of message blocks which is of sufficient size to store the message data; and

first message control transfer means for transferring said shared memory block index to said datagram socket interprocess communications mechanism.

3. The system of claim 2, wherein said receiving means comprises:

second message control transfer means for transferring said shared memory block index from said datagram socket interprocess communications mechanism to the destination user process;

second message transfer means for transferring the message from said allocated message block and from said temporary buffer to a local memory location associated with the destination user process; and

second memory allocation means for releasing said allocated message block.

4. An interprocess communications system for transferring a message from a source user process to a destination process, comprising:

a shared memory having one or more shared memory blocks, each of said one or more message blocks having a preamble portion and a message content portion configured to store message data;

a datagram socket associated with said destination process;

a message origination interprocess communications mechanism associated with the user process, coupled to said shared memory and to said datagram socket, comprising;

a source memory allocation subsystem configured to allocate one of said one or more shared memory blocks from said shared memory to transfer the message, said allocated shared memory block having a location identified by a shared memory block index,

a source message transfer subsystem configured to transfer said message located at a local memory address designated by said user process to said allocated shared memory block, and

a source datagram transfer subsystem configured to place said shared memory block index into said datagram socket;

a message reception interprocess communications mechanism associated with said destination user process, coupled to said shared memory and to said datagram socket, comprising,

a destination datagram transfer subsystem configured to retrieve said shared memory block index from said datagram socket,

a destination message transfer subsystem configured to transfer the message from said shared memory block identified by said shared memory block index to a designated local memory address associated with the destination user process, and

a destination memory allocation subsystem configured to release said shared memory block previously containing the message for future use when no other destination user process is to receive the message.

5. The system of claim 4, wherein said memory allocation subsystem locks access to said shared memory block and updates said preamble of said shared memory block to indicate an in-use status of said shared memory block, the current time, the allocating process ID, and the number of receivers that are to receive the message block.

6. The system of claim 4, wherein said datagram transfer subsystem outputs a status of said datagram transmission to the source user process.

7. The system of claim 4, wherein said datagram transfer subsystem decrements a shared memory block preamble receiver count by one, said datagraph transfer subsystem indicating said shared memory block is available when said receiver count is zero.

8. The system of claim 4, wherein said datagram socket is identified by a datagram socket address received from said destination user process.

9. The system of claim 4, wherein said destination memory allocation subsystem releases said shared memory block when all destination user processes have received said message, thereby making said shared memory block available for re-use by another user process.

10. An interprocess communications system for transferring message data from a source user process to at least one destination user process in a computer-based system, the interprocess communications system comprising:

initialization means for creating and initializing a shared memory segment in a shared memory; and

sending means for placing the message data to said shared memory segment and for placing message control data to a control data interprocess communications (IPC) transfer mechanism having a connectionless packetized protocol.

11. The system of claim 10, further comprising:

user process initialization means for attaching the source user process and the destination user process to said shared memory segment for each message data transfer; and

receiving means for receiving said message control data from said control data IPC transfer mechanism and for using said message control data to retrieve the message data from said shared memory segment.

12. The system of claim 11, wherein said message control data comprises a shared memory block index identifying the location of said allocated message blocks containing the message data in the shared memory.

13. The system of claim 12, wherein said shared memory segment comprises one or more message blocks, each of said one or more message blocks having a preamble portion and a message content portion configured to store the message data.

14. The system of claim 13, wherein said preamble portion comprises:

an availability status region configured to contain an availability status of an associated message block;

a time allocation region configured to contain the time at which an associated message block has been allocated by a first memory allocation means;

an identification region configured to contain the identity of the source user process for which said associated message block has been allocated; and

a receiving count region configured to contain a number of remaining destination processes to receive said associated message block.

15. The system of claim 14, wherein said sending means comprises:

first memory allocation means for allocating at least one of said plurality of message blocks, said allocated message blocks being of sufficient size to store the message data;

first message transfer means for transferring the message dam from a local memory location associated with the source user process to said allocated message blocks, and for placing the message data in a temporary buffer when said first memory allocation means cannot allocate message blocks of sufficient size and when the source user process has messages presently pending to be transferred; and

first message control transfer means for transferring said message control data to said control data IPC transfer mechanism.

16. The system of claim 15, wherein said receiving means comprises:

second message control transfer means for transferring said message control data from said control data IPC transfer mechanism to the at least one destination user process;

second message transfer means for transferring the message data from said allocated message blocks to a local memory location associated with the destination user process; and

second memory allocation means for releasing said allocated message blocks.

17. The system of claim 16, further comprising:

maintenance means for maintaining the availability of said plurality of message blocks in said shared memory segment, said maintenance means periodically reading said time in said time allocation region and comparing said time to a predetermined value; and

shutdown means for performing a controlled shutdown of the interprocess communications when the associated user process ceases execution, said shutdown means guaranteeing that all messages associated with said associated user process are sent to the at least one destination user process before said associated user process is terminated.

18. The system of claim 17, wherein the computer-based system provides a Unix operating system environment and wherein the implementation of the interprocess communications system is achieved utilizing Unix operating system features.

19. The system of claim 18, wherein said control data IPC transfer mechanism is a datagram socket interprocessor communications mechanism.

29. The system of claim 10, wherein said message control data is a shared memory block index, said shared memory block index identifying a location at which the message data is stored in said shared memory.

20. A method for transferring a message from a source user process to at least one destination user process in a computer-based system having a shared memory, the method comprising the steps of:

(1) initializing a shared memory segment in the shared memory by a memory allocation subsystem;

(2) placing the message in said shared memory segment by a message transfer subsystem; and

(3) placing message control data in a control data interprocess communications (IPC) transfer mechanism having a connectionless packetized protocol.

21. The method of claim 20, further comprising the step of:

(4) receiving said message control data from said control data IPC transfer mechanism and using said message control data to retrieve the message data placed in said shared memory segment.

22. The method of claim 21, wherein said step (1) comprises the steps of:

(a) dividing said shared memory segment into one or more message blocks,

(b) creating a segment descriptor identifying said allocated shared memory segment,

(c) dividing each of said one or more message blocks into a preamble portion and a message content portion, said preamble portion including an availability status region, and

(d) transferring said segment descriptor to the source user process and the at least one destination user process.

23. The method of claim 21, wherein said step (2) comprises the steps of:

(a) receiving an address of a first local memory location associated with the source user process, the length of the message, and a source user process identifier from the source user process, said first local memory location containing the message data;

(b) determining which of said plurality of message blocks are available, and allocating from said available message blocks a message block sufficient to store the message data;

(c) transferring the message data from said first local memory location to said allocated message block;

(d) updating, for said allocated message block, said availability status region with an unavailable status, updating a time allocation status region with the time of allocation, and updating a user process identification region with a source user process identifier.

24. The method of claim 23, wherein said step (2) further comprises the steps of:

(e) allocating a temporary buffer to store the message data if the source user process presently has messages to be transferred and when said plurality of message blocks do not contain a message block of sufficient size to store the message data, said temporary buffer enqueued with other pending messages to be transferred from the source user process;

(f) providing said status indication to the source user process indicating a successful message transfer when the message data has been transferred to said temporary buffer; and

(g) transferring said enqueued message data from said temporary buffer to said allocated message block when said available message blocks are allocated.

25. The method of claim 24, further comprising the step of:

(5) shutting down the interprocess communications system when the source user process ceases execution, comprising the steps of;

a) repeating step (g) until all message data enqueued in said temporary buffers have been transferred;

b) removing said control data IPC transfer mechanism; and

c) detaching the source user process from said shared memory segment.

26. The method of claim 25, further comprising the step of:

(6) maintaining the availability of said plurality of message blocks in said shared memory segment, comprising the steps of;

(a) periodically reading said time allocation region and comparing said time to a predetermined value; and

(b) updating, for each of said allocated message blocks wherein said time is greater than said predetermined value, said availability status region with an available status.

27. The method of claim 21, wherein said message control data comprises a shared memory block index identifying the location of said shared memory segment containing the message.

28. The method of claim 21, wherein said control data IPC transfer mechanism is datagram socket IPC mechanism.