Driver Sub-Device Interface for GPU State Querying
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems for managing multiple graphics processors restrict applications from querying individual processors, limiting their ability to access sub-device state information such as performance, temperature, and power information, which is essential for efficient operation.
Innovation Solution
A system and method that utilizes a driver to expose sub-devices to applications, allowing them to request and receive state information from individual graphics processors or graphics processing units (GPUs), enabling direct communication and operation in both master-slave and independent modes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a driver is used to provide interoperability among multiple graphics processors and single processor-equipped applications, then compatibility and ease of operation are improved, but the ability to query individual processor state information is lost
Solution Approach 1:
The driver segments the monolithic device view into sub-device views, allowing applications to query individual graphics processors while maintaining the aggregated device interface. The driver divides the device information into separate sub-device entities, each representing a physical graphics processor, enabling selective state information retrieval without breaking compatibility.
2Reliability
If applications are restricted to querying only the aggregated device, then driver interoperability is maintained, but measurement precision and access to specific processor states are reduced
Solution Approach 1:
The driver adds a new dimension to the device interface by introducing sub-device levels. Applications can now query at two dimensions: the aggregated device level for overall status and individual sub-device levels for specific processor states. This dimensional expansion allows precise state information retrieval while preserving the original interoperability interface.
3Ease of operation
If the driver exposes only a single device interface, then application simplicity is maintained, but adaptability to multi-processor operations is limited
Solution Approach 1:
The driver implements a universal interface that serves multiple functions: it maintains the traditional single-device aggregation view for simple applications while simultaneously exposing sub-device views for applications requiring multi-processor capabilities. This multi-functional interface design allows the same driver to serve both simple and advanced use cases without requiring separate implementations.
Data Source
AI summary
A system, method, and computer program product are provided for communicating sub-device state information. In use, a plurality of sub-devices of a device is exposed to an application, utilizing a driver. A request may then be received from the application for state information associated with at least one of the sub-devices. In response to the request, the state information is provided to the application.