AF UNIX Socket Across Systems in the Same Computer on Computer Systems that Support Multiple Operating System Images

• US 20080155103A1
• Filed: 12/21/2006
• Published: 06/26/2008
• Est. Priority Date: 12/21/2006
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bailey, Kimberly Tekavec
• Application Number:
  US11/614,228
• Publication Number:
  US 20080155103A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes
• 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

Abstract

The present invention is directed to a system, method and software program product for extending the use of Unix domain sockets to support multiple operating system images. An application creates a Unix domain socket using the sockets system call and binds the socket to a system file pathname for a service using an appropriate system call. The system file pathname represents the connection binding to the service. The operating system running the application may recognize that the service does not reside on the same operating system image and, therefore, a Unix domain socket cannot be used to communicate. To the operating system the system file pathname represents the binding that translates to a pathname that represents a real I/O device for cross-system communications. The operating system translates the system file pathname to a device pathname for the service. An appropriate transport is selected for the device and the transport invokes the point-to-point I/O device. Interprocess communication can then proceed.

Claims

1. A method for extending Unix domain sockets for communication, comprising:

receiving a Unix domain system call from a process to establish communication with a second process;

recognizing a file system pathname in the system call;

translating the file system pathname to a real I/O device pathname for communication with the second process; and

establishing a connection for the second process using the device pathname.

2. The method recited in claim 1 further comprising:

determining the device pathname for the second process from the system pathname.

3. The method recited in claim 1 further comprising:

finding the device pathname for the second process from a plurality of device pathnames for a plurality of unique services.

4. The method recited in claim 1, wherein the process and second process are running on different operating system images.

5. The method recited in claim 1 wherein the device pathname comprises an identifier for the process and an identifie for the second process and an identifier for a communication channel.

6. The method recited in claim 1, further comprising:

binding to a communication channel.

7. The method recited in claim 6, wherein the communication channel is a real Input/Output (I/O) device between the first process and the second process.

8. The method recited in claim 1 wherein establishing a connection for the second process using the device pathname further comprises:

selecting a cross-system transport for the device pathname; and

invoking a real I/O device between the process and the second process.

9. The method recited in claim 1 further comprising:

receiving a second Unix domain system call from the process to establish communication with a third process;

recognizing a second file system pathname in the second system call; and

establishing a connection for the third process using the second files system pathname.

10. A computer program product for extending Unix domain sockets for communication, said computer program product comprising:

a computer usable medium having computer useable program code embodied therewith, the computer usable program code comprising;

computer usable program code to receive a Unix domain system call from a process to establish communication with a second process;

computer usable program code to recognize a file system pathname in the system call;

computer usable program code to translate the file system pathname to a real I/O device pathname for communication with the second process; and

computer usable program code to establish a connection for the second process using the device pathname.

11. The computer program product recited in claim 10 further comprising:

computer usable program code to determine the device pathname for the second process from the system pathname.

12. The computer program product recited in claim 10 further comprising:

computer usable program code to find the device pathname for the second process from a plurality of device pathnames for a plurality of unique services.

13. The computer program product recited in claim 10, wherein the process and second process are running on different operating system images.

14. The computer program product recited in claim 10, wherein the device pathname comprises an identifier for the process and an identifier for the second process and an identifier for a communication channel.

15. The computer program product recited in claim 10, further comprising;

computer usable program code to bind to a communication channel.

16. The computer program product recited in claim 15, wherein the communication channel is a real Input/Output (I/O) device between the first process and the second process.

17. The computer program product recited in claim 10, wherein the computer usable program code to establish a connection for the second process using the device pathname further comprises:

computer usable program code to select a cross-system transport for the device pathname; and

invoking a real I/O device between the process and the second process.

18. The computer program product recited in claim 10, further comprising:

computer usable program code to receive a second Unix domain system call from the process to establish communication with a third process;

computer usable program code to recognize a second file system pathname in the second system call; and

computer usable program code to establish a connection for the third process using the second files system pathname.

19. A system for extending Unix domain sockets for communication comprising:

a first operating system image with a first application running on the first operating system image, Unix file system, a first Unix cross memory transport for invoking the Unix file system, a first point-to-point input/output device, a first Unix domain cross system transport for invoking the first point-to-point input/output device, and a first Unix domain physical file system with logic for receiving system calls from the first application and selecting one of the first Unix cross memory transport and the first Unix domain cross system transport for establishing a connection; and

a second operating system image with a second application running on the second operating system images Unix file system, a second Unix cross memory transport for invoking the Unix file system, a second point-to-point input/output device a second Unix domain cross system transport for invoking the second point-to-point input/output device, and a second Unix domain physical file system with logic for receiving system calls from the second application and selecting one of the second Unix cross memory transport and the second Unix domain cross system transport for establishing a connection.

20. A system recited in claim 19 above, wherein the first and second Unix domain physical file systems further comprise logic for recognizing a file system pathname in a system call and for translating the recognized file system pathname to a real I/O device pathname.