1. A method for accessing a device, comprising:
creating a corresponding global unique identifier root bus object for each of a plurality of root buses in a system to which the device may be coupled, wherein each root bus is capable of having one or more devices coupled thereto, wherein each globally unique identifier root bus object includes an object-oriented abstraction that identifies a plurality of methods that may be used to determine a configuration of the corresponding root bus and to determine resource requirements of the corresponding root bus;
sending a resource access request to a device driver or OPROM corresponding to the device;
sending a resource access command corresponding to the resource access request from the device driver or OPROM to an abstraction layer interface;
verifying whether a resource operation corresponding to the resource access command is authorized to be performed on the device;
determining a resource access method(s) that may be implemented to cause the device to perform the resource operation, wherein the resource access method(s) is responsive to at least one created global unique identifier root bus object; and
calling the resource access method(s) to perform the resource operation on the device;
wherein the abstraction layer interface hides the resource access method(s) from the device driver or OPROM.
2. The method of claim 1, wherein the resource access request comprises requesting data to be read from the device, further comprising returning data read from the device to the device driver or OPROM.
3. The method of claim 1, wherein the abstraction layer interface includes a database from which resource access methods corresponding to the device can be determined.
4. The method of claim 1, wherein the abstraction layer interface includes a database containing data corresponding to a configuration of a root bus to which the device is directly or indirectly connected and resource information corresponding to any devices in a hierarchy of the root bus.
5. The method of claim 4, wherein the data corresponding to the root bus configuration and resources is represented by an object-oriented abstraction comprising a set of components that includes reference to one or more configuration methods that may be implemented to obtain andor generate configuration and resource allocation information for the root bus and any devices and subordinate buses in the root bus hierarchy.
6. The method of claim 1, wherein the abstraction layer interface hides resource access methods for the device from the device driver or OPROM so that the device driver or OPROM may not directly access the device with those access methods.
7. A method for providing access to devices in a system that includes a plurality of root buses, comprising:
creating a corresponding global unique identifier root bus object for each of the plurality of root buses, wherein each root bus is capable of having one or more devices coupled thereto, wherein each globally unique identifier root bus object includes an object-oriented abstraction that identifies a plurality of methods that may be used to determine a configuration of the corresponding root bus and to determine resource requirements of the corresponding root bus:
storing configuration and resource information corresponding to each of said plurality of root buses and any devices and subordinate buses in a hierarchy for that root bus;
providing an abstraction layer interface that enables device drivers or OPROMs corresponding to the devices to perform resource operations on the devices through resource access methods corresponding to those devices, wherein the resource access methods is responsive to at least one created global unique identifier root bus object, said abstraction layer hiding such resource access methods from the device drivers or OPROMs so as to prevent the device drivers or OPROMs from directly implementing the resource access methods to perform resource operations on their corresponding devices;
passing identification information and one or more resource access commands from one or more of the device drivers or OPROMs to the abstraction layer interface;
verifying whether a resource operation to be performed on one of the devices, the one of the devices corresponding to said one or more resource access commands is authorized based on the identification information and the configuration and resource information that is stored; and
performing the resource operation on the device if it is authorized to be performed, the resource operation being performed on the device in a manner such that the abstraction layer interface hides the resource access method(s) from the device driver or OPROM.
8. The method of claim 7, wherein the configuration and resource information for each root bus is represented as an object-oriented abstraction comprising a set of components that includes reference to one or more configuration methods that may be implemented to obtain or generate configuration and resource information for the root bus and any devices and subordinate buses in the root bus hierarchy.
9. The method of claim 8, wherein the object-oriented abstractions for the root buses are stored in a database that is accessible by the abstraction layer interface.
10. The method of claim 9, further comprising providing a record for each device in the database identifying the device, a device driver or OPROM for the device, and the object-oriented abstraction corresponding to the root bus for the device.
11. The method of claim 7, further comprising publishing a public interface method that enables device drivers or OPROMs to access devices via the abstraction layer interface by passing identification, resource, and resource access command(s) to the abstraction interface.
12. An article of manufacture comprising a computer-readable medium having computer-executable instructions that when executed enable access to a device by:
creating a corresponding global unique identifier root bus object for each of a plurality of root buses in a system to which a device may be coupled, wherein each root bus is capable of having one or more devices coupled thereto, wherein each globally unique identifier root bus object includes an object-oriented abstraction that identifies a plurality of methods that may be used to determine a configuration of the corresponding root bus and to determine resource requirements of the corresponding root bus;
sending a resource access request to a device driver or OPROM corresponding to the device;
sending a resource access command corresponding to the resource access request from the driver to an abstraction layer interface;
verifying whether a resource operation corresponding to the resource access command is authorized to be performed on the device;
determining a resource access method(s) that may be implemented to cause the device to perform the resource operation, wherein the resource access method(s) is responsive to at least one created global unique identifier root bus object; and
calling the resource access method(s) to perform the resource operation on the device in a manner such that the abstraction layer interface hides the resource access method(s) from the device driver or OPROM.
13. The article of manufacture of claim 12, wherein the resource access request comprises requesting data to be read from the device, and wherein execution of the instructions further performs the function of returning data read from the device to the device driver or OPROM.
14. The article of manufacture of claim 12, wherein execution of the instructions further performs the function of creating a database containing data corresponding to a configuration of a root bus to which the device is directly or indirectly connected to and resource information corresponding to any devices in a hierarchy of the root bus.
15. The article of manufacture of claim 12, wherein the data corresponding to the root bus configuration and resources is represented by an object-oriented abstraction comprising a set of components that includes reference to one or more configuration methods that may be implemented to obtain andor generate configuration and resource allocation information for the root bus and any devices and subordinate buses in the root bus hierarchy.
16. The article of manufacture of claim 12, wherein the abstraction layer interface hides resource access methods for the device from the device driver or OPROM so that the device driver or OPROM may not directly access the device with those access methods.
17. An article of manufacture comprising a computer-readable medium having computer-executable instructions that when executed provide access to devices in a system that includes a plurality of root buses by;
creating a corresponding global unique identifier root bus object for each of a plurality of root buses in a system to which a device may be coupled, wherein each root bus is capable of having one or more devices coupled thereto, wherein each globally unique identifier root bus object includes an object-oriented abstraction that identifies a plurality of methods that may be used to determine a configuration of the corresponding root bus and to determine resource requirements of the corresponding root bus;
storing configuration and resource information corresponding to each of said plurality of root buses and any devices and subordinate buses in a hierarchy for that root bus;
providing an abstraction layer interface that enables device drivers or OPROMs for the devices to perform resource operations on the devices through resource access methods corresponding to those devices, said abstraction layer hiding such resource access methods from the device drivers or OPROMs so as to prevent the device drivers or OPROMs from directly implementing the resource access methods to perform resource operations on their corresponding devices, wherein the resource access methods are responsive to at least one created global unique identifier root bus object;
passing identification information and one or more resource access commands from the device drivers or OPROMs to the abstraction layer interface;
verifying whether a resource operation(s) to be performed on a device corresponding to said one or more resource access commands is authorized based on the identification information and the configuration and resource information that is stored; and
performing the resource operation on the device if it is authorized to be performed, the resource operation being performed in a manner such that the abstraction layer interface hides the resource access method(s) from the device driver or OPROM.
18. The article of manufacture of claim 17, wherein the configuration and resource information for each root bus is represented as an object-oriented abstraction comprising a set of components that includes reference to one or more configuration methods that may be implemented to obtain andor generate configuration and resource information for the root bus and any devices and subordinate buses in the root bus hierarchy.
19. The article of manufacture of claim 18, wherein the object-oriented abstractions for the root buses are stored in a database that is accessible by the abstraction layer interface, and execution of the instructions further performs the function of providing a record for each device in the database identifying the device, a device driver or OPROM for the device, and the object-oriented abstraction corresponding to the root bus for the device.
20. A computer system comprising:
a memory in which a plurality of instructions are stored;
a device;
a root bus to which the device is operatively coupled; and
a processor connected to the root bus and the memory, said plurality of instructions when executed by the processor causing functions to be performed including:
creating a global unique identifier root bus object for the root bus, wherein the globally unique identifier root bus object includes an object-oriented abstraction that identifies a plurality of methods that may be used to determine a configuration of the root bus and to determine resource requirements of the root bus;
sending a resource access request to a device driver or OPROM corresponding to the device;
sending a resource access command corresponding to the resource access request from the device driver or OPROM to an abstraction layer interface;
verifying whether a resource operation corresponding to the resource access command is authorized to be performed on the device;
determining a resource access method(s) that may be implemented to cause the device to perform the resource operation, wherein the resource access method(s) is responsive to at least one created global unique identifier root bus object; and
calling the resource access method(s) to perform the resource operation on the device in a manner such that the abstraction layer interface hides the resource access method(s) from the device driver or OPROM.
21. The system of claim 20, wherein the resource access request comprises requesting data to be read from the device, and wherein execution of the instructions further performs the function of returning data read from the device to the device driver or OPROM.
22. The system of claim 20, wherein execution of the instructions further performs the function of creating a database containing data corresponding to a configuration of a root bus to which the device is directly or indirectly connected to and resource information corresponding to any devices in a hierarchy of the root bus.
23. The system of claim 20, wherein the data corresponding to the root bus configuration and resources is represented by an object-oriented abstraction comprising a set of components that includes reference to one or more configuration methods that may be implemented to obtain andor generate configuration and resource allocation information for the root bus and any devices and subordinate buses in the root bus hierarchy.
24. The system of claim 20, wherein the abstraction layer interface hides resource access methods for the device from the device driver or OPROM so that the device driver or OPROM may not directly access the device with those access methods.
25. A computer system comprising:
a memory in which a plurality of instructions are stored;
a plurality of root buses;
a plurality of devices connected to the root buses; and
a processor connected to the root buses and the memory, said plurality of instructions when executed by the processor causing functions to be performed including:
creating a corresponding global unique identifier root bus object for each of the plurality of root buses, wherein each globally unique identifier root bus object includes an object-oriented abstraction that identifies a plurality of methods that may be used to determine a configuration of the corresponding root bus and to determine resource requirements of the corresponding root bus;
storing configuration and resource information corresponding to each of said plurality of root buses and any devices and subordinate buses in a hierarchy for that root bus;
providing an abstraction layer interface that enables device drivers or OPROMs for the devices to perform resource operations on the devices through resource access methods corresponding to those devices, said abstraction layer hiding such resource access methods from the device drivers or OPROMs so as to prevent the device drivers or OPROMs from directly implementing the resource access methods to perform resource operations on their corresponding devices, wherein the resource access methods are responsive to at least one created global unique identifier root bus object;
passing identification information and resource access command(s) from device drivers or OPROMs to the abstraction layer interface;
verifying whether a resource operation to be performed on a device corresponding to the resource access command(s) is authorized based on the identification information and the configuration and resource information that is stored; and
performing the resource operation on the device if it is authorized to be performed, the resource operation being performed in a manner such that the abstraction layer interface hides the resource access method(s) from the device driver or OPROM.
26. The system of claim 25, wherein the configuration and resource information for each root bus is represented as an object-oriented abstraction comprising a set of components that includes reference to one or more configuration methods that may be implemented to obtain andor generate configuration and resource information for the root bus and any devices and subordinate buses in the root bus hierarchy.
27. The system of claim 26, wherein the object-oriented abstractions for the root buses are stored in a database that is accessible by the abstraction interface layer, and execution of the instructions further performs the function of providing a record for each device in the database identifying the device, a device driver or OPROM for the device, and the object-oriented abstraction corresponding to the root bus for the device.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A process for producing an olefin polymer which comprises continuously polymerizing an olefinic monomer in the presence of a polymerization catalyst obtained by contact treatment of a transition metal compound and a co-catalyst component in a polymerization reaction tank in which an agitation shaft having an agitating blade is suspended in the central part of the tank, wherein the agitating blade is disposed close to the bottom surface of the polymerization reaction tank at a distance between the lower end portion of the agitating blade and the bottom surface of the polymerization reaction tank of 0.1\xd7D or less where D is the diameter of the polymerization reaction tank, the transition metal compound and the co-catalyst component are respectively fed to the positions of the bottom of the polymerization reaction tank which are at a distance of 0.5\xd7d or less from the center of the agitation shaft where d is a diameter of the agitating blade, and the agitation is carried out at a Reynolds number for agitation of 100 or more.
2. A process for producing an olefin polymer according to claim 1, wherein the distance between the bottom surface of the polymerization reaction tank and the lower end portion of the agitating blade is 0.05\xd7D or less where D is the diameter of the polymerization reaction tank.
3. A process for producing an olefin polymer according to claim 1 or 2, wherein the transition metal compound is a compound having a ligand having a cyclopentadiene anion skeleton.