Thread-safe portable management interface
First Claim
1. A thread-safe scheduler system, comprising:
- at least one processor; and
memory coupled to the at least one processor, wherein the memory is configured to store program instructions executable by the at least one processor to implement;
a primary scheduler which is executable to schedule requests for networked data resources; and
a secondary scheduler, wherein the secondary scheduler is executable to receive a plurality of requests from a multi-threaded application in a thread-safe manner and send the requests received from the multi-threaded application to the primary scheduler in a thread-safe manner;
wherein the requests comprise callback functions, and wherein the callback functions are executable to send responses to the requests to the multi-threaded application.
2 Assignments
0 Petitions
Accused Products
Abstract
A system and method for using a management interface such as Portable Management Interface (PMI) in a thread-safe and efficient manner. A secondary scheduler receives PMI management requests from multi-threaded manager applications in a thread-safe manner, such as through a lock. The secondary scheduler monitors the flow of PMI-related requests into PMI to ensure that, at any point in time, only one management request (e.g., callback function) is running on the PMI thread. When a request in the secondary queue is ready for scheduling with the primary scheduler, the secondary scheduler then accesses the primary scheduler in a thread-safe manner, such as through a lock, to send the request to the primary scheduler. The management requests are dispatched from the primary scheduler and executed on managed objects though a Management Information Server. The performance and efficiency of the manager applications is enhanced by increasing the responsiveness of interaction between the manager applications and the schedulers. The performance of the management interface is enhanced by eliminating the need for polling-based scheduling solutions.
62 Citations
35 Claims
-
1. A thread-safe scheduler system, comprising:
-
at least one processor; and memory coupled to the at least one processor, wherein the memory is configured to store program instructions executable by the at least one processor to implement; a primary scheduler which is executable to schedule requests for networked data resources; and a secondary scheduler, wherein the secondary scheduler is executable to receive a plurality of requests from a multi-threaded application in a thread-safe manner and send the requests received from the multi-threaded application to the primary scheduler in a thread-safe manner; wherein the requests comprise callback functions, and wherein the callback functions are executable to send responses to the requests to the multi-threaded application. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13)
-
-
14. A thread-safe method for using a management interface for management of a plurality of managed objects on a network, the method comprising:
-
receiving a plurality of management requests from a multi-threaded manager application into a secondary scheduler in a thread-safe manner; scheduling the plurality of management requests in a secondary queue in the secondary scheduler after receiving the management requests from the manager application; sending the management requests from the secondary scheduler to a primary scheduler in a thread-safe manner; scheduling the management requests in a primary queue in the primary scheduler, wherein each of the management requests comprises a corresponding callback function; and executing the management requests on the managed objects after scheduling the management requests in the primary queue. - View Dependent Claims (15, 16, 17, 18, 19, 20, 21, 22, 23, 24)
-
-
25. A tangible, computer-readable storage medium comprising program instructions, wherein the program instructions are computer-executable to implement:
-
receiving a plurality of management requests from a multi-threaded manager application into a secondary scheduler in a thread-safe manner; scheduling the plurality of management requests in a secondary queue in the secondary scheduler after receiving the management requests from the manager application; sending the management requests from the secondary scheduler to a primary scheduler in a thread-safe manner; scheduling the management requests in a primary queue in the primary scheduler, wherein each of the management requests comprises a corresponding callback function; and executing the management requests on the managed objects after scheduling the management requests in the primary queue. - View Dependent Claims (26, 27, 28, 29, 30, 31, 32, 33, 34, 35)
-
Specification