System and method for transparent, global access to physical devices on a computer cluster

• US 6,163,806 A
• Filed: 06/30/1997
• Issued: 12/19/2000
• Est. Priority Date: 06/30/1997
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Viswanathan, Srinivasan, Nazari, Siamak, Khalidi, Yousef, Swaroop, Anil
• Primary Examiner(s): Asta, Frank J.
• Assistant Examiner(s): VU, THONG H
• Application Number:
  US08/885,024
• Time in Patent Office: 1,268 Days
• Field of Search: 395/500, 395/701, 395/200.38, 395/600, 395/653, 395/706, 395/182.02, 364/200, 711/165, 707/10, 370/255, 370/331, 709/169, 709/229, 379/207
• US Class Current: 709/229
• CPC Class Codes: G06F 9/4411 Configuring for operating with peripheral devices; Loading of device drivers

Abstract

A system and method are disclosed that provides transparent, global access to devices on a computer cluster. The present system generates unique device type (dev_-- t) values for all devices and corresponding links between a global file system and the dev_-- t values. The file system is modified to take advantage of this framework so that, when a user requests that a particular device, identified by its logical name, be opened, an operating system kernel queries the file system to determine that device'"'"'s dev_-- t value and then queries the a device configuration system (DCS) for the location (node) and identification (local address) of a device with that dev_-- t value. Once it has received the device'"'"'s location and identification, the kernel issues an open request to the host node for the device identified by the DCS. File system components executing on the host node, which include a special file system (SpecFS), handle the open request by returning to the kernel a handle to a special file object that is associated with the desired device. The kernel then returns to the requesting user a file descriptor that is mapped to the handle, through which the user can access the device.

Claims

1. A system configured to provide global access to physical devices located on a computer cluster comprising a plurality of nodes, the system comprising:

a global file system;

a device configuration system (DCS), the DCS storing physical device information for a plurality of physical devices, the physical device information for each device in the plurality including a major number associated with a device type assigned to the physical device and other devices of same type, and a minor number that is globally unique for physical devices having the same major number;

the physical devices including a plurality of physical devices having a same major number associated therewith including at least one device having a first globally unique minor number associated therewith on a first node of the system and a second device having a second globally unique minor number associated therewith on a second node of the system;

at least one device server object (DSO) on each node of the system;

the global file system including an interface for responding to a request to access one such physical device issued from one of the nodes by sending a corresponding request to the DCS;

the DCS including an interface for responding to the request by returning information corresponding to the major number and globally unique minor number associated with the requested physical device, and also determining which node the physical device resides on and the DSO to use to access the physical device;

the global file system including means for using the information returned by the DCS to generate a file descriptor and for returning the file descriptor for subsequent use in accessing the requested physical device.

2. The system of claim 1, wherein the DCS is hosted on one of the nodes, the system further comprising:

a common operating system kernel running on each of the nodes in the computer cluster;

a device driver interface (DDI) running on each of the nodes; and

a plurality of device drivers located on each of the nodes, each of the device drivers being configured to manage one type of physical device and being associated with a unique, major number;

each device driver being configured, when a new device of an appropriate type is attached to a respective node, to issue an attach message to the DDI indicating a local identifier (locid) of the new device being attached;

the DDI being configured, in response to the attach message, to issue a map request to the DCS for the unique global minor (gmin) number for the attached device, the map request indicating the major number and the locid of the device being attached;

the DCS being configured, in response to the map request, to (a) determine the gmin number, (b) return the gmin number to the DDI, and (c) store the gmin number, the major number and the gmin number;

the DDI being configured to associate the gmin number returned by the DCS and the major number with the attached device so that the attached device is accessible from the file system in response to a request to open the attached device.

3. The system of claim 1, wherein the DCS, file system and requested device are each on different nodes, the system further comprising a proxy file system enabling applications on one node to communicate transparently with file objects co-located with the requested device on another node.

4. The system of claim 1, wherein the at least one DSO comprises a set of device server objects on each node of the cluster, each of which manages a respective device class.

5. The system of claim 4, wherein the device class is a member of a set of device classes including at least one of:

"dev_-- enumerate," for designating devices with at least one occurrence managed by a particular driver, each of the occurrences managed by the particular driver on a particular node being individually enumerated;

"dev_-- nodespecific," for designating devices available on each node that are accessed locally and have a one-to-one relationship with the managing device driver on each node;

"dev_-- global," for designating devices that can be accessed by such device drivers from on any such node; and

"dev_-- nodebound," designating devices that are accessed by a driver on a particular node and have a one-to-one relationship with the device driver.

6. The system of claim 4, wherein:

the device driver includes means for issuing device configuration information to the DDI including a class, if available, for the device;

the DDI has means for including the class, if available, in a map request to the DCS.

7. A method configured to provide global access to physical devices located on a computer cluster comprising a plurality of nodes, the method comprising the steps of:

storing in a device configuration system (DCS) physical device information for a plurality of the physical devices, the physical device information for each device in the plurality including a major number associated with a device type assigned to the physical device and other devices of same type, and a minor number that is globally unique for physical devices having the same major number;

the physical devices including a plurality of physical devices having a same major number associated therewith including at least one device having a first globally unique minor number associated therewith on a first node of the system and a second device having a second globally unique minor number associated therewith on a second node of the system;

a global file system responding to a request to access one such physical device issued from one of the nodes by requesting a DSO handle from a device configuration system (DCS);

the DCS determining in response to the access request an identity of a first device server object (DSO) associated with the requested physical device and returning to the global file system a reference to the first DSO and information corresponding to the major number and globally unique minor number associated with the requested physical device;

the global file system using the information returned by the DCS to generate a file descriptor and returning the file descriptor for subsequent use in accessing the requested physical device.

8. The method of claim 7, wherein the DCS is hosted on one of the nodes, the method further comprising the steps of:

each of a plurality of device drivers, when a new device of an appropriate type is attached to a respective node, issuing an attach message to a co-located device driver interface (DDI) indicating a local identifier (locid) of the new device being attached, each of the device drivers being configured to manage one type of physical device and being associated with a unique, major number;

the DDI, in response to the attach message, issuing a map request to the DCS for the unique global minor (gmin) number for the attached device, the map request indicating the major number and the locid of the device being attached;

the DCS, in response to the map request;

(a) determining the gmin number, (b) returning the gmin number to the DDI, and (c) storing the gmin number, the major number and the gmin number;

the DDI associating the gmin number returned by the DCS and the major number with the attached device so that the attached device is accessible from the file system in response to a request to open the attached device.

9. The method of claim 7, wherein the DCS, file system and requested device are each on different nodes, further comprising the step of enabling applications on one node to communicate transparently with file objects co-located with the requested device on another node.

10. The method of claim 7, wherein the at least one DSO comprises a set of device server objects on each node of the cluster, each of which manages a respective device class.

11. The method of claim 10, wherein the device class is a member of a set of device classes including:

"dev_-- enumerate," for designating devices with at least one occurrence managed by a particular driver, each of the occurrences managed by the particular driver on a particular node being individually enumerated;

"dev_-- nodespecific," for designating devices available on each node that are accessed locally and have a one-to-one relationship with the managing device driver on each node;

"dev_-- global," for designating devices that can be accessed by such device drivers from on any such node; and

"dev_-- nodebound," designating devices that are accessed by a driver on a particular node and have a one-to-one relationship with the device driver.

12. The method of claim 10, further comprising the steps of:

the device driver issuing device configuration information to the DDI including a class, if available, for the device; and

the DDI including the class information, if available, in a map request to the DCS.

13. The method of claim 12, further comprising the steps of:

upon receiving the map request, the DCS consulting a local DSO associated with the same class; and

the local DSO determining a global minor number to be assigned to the device being attached.

14. The method of claim 13, further comprising the step of:

when the class information is not provided by the device driver, accessing the corresponding device as if the corresponding device were of a dev_-- enumerate class including devices with at least one occurrence managed by a particular driver, each of the occurrences managed by the particular driver on a particular node being individually enumerated.

15. The system of claim 8, further comprising the step of:

when the open request is issued on a requested device identified by logical name, querying the file system to determine a dev_-- t value of the requested device;

and querying the DCS for the location and identification of a device with the dev_-- t value of the requested device.

16. The system of claim 15, wherein:

once it has received the location and identification of the requested device, the kernel issues an open request to a host node for the requested device.

17. The system of claim 16, further comprising:

file system components executing on the host node, including a special file system (SpecFS) configured to handle the open request by returning to the kernel a handle to a special file object that is associated with the requested device.

18. The system of claim 17, wherein:

the kernel returns a file descriptor that is mapped to the handle, through which the requested device can be accessed.