South-Side Management Data Array for PCI Virtualization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The Peripheral Component Interconnect (PCI) standard does not provide definitions for managing device-specific data below the PCI hierarchy, known as south-side management, which is crucial for operating I/O virtualization-enabled adapters effectively.
Innovation Solution
A mechanism is defined to manage south-side device-specific functions using a Single Root Peripheral Component Interconnect Manager (SR-PCIM) or Multiple Root PCI Manager (MR-PCIM), which includes a new data structure for the adapter's configuration space that allows platform-specific code to infer device types and manage south-side resources, enabling efficient management of I/O virtualization-enabled devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If PCI standard is used for I/O adapter management, then compatibility with existing systems is maintained, but south-side device-specific data management capability is insufficient
Solution Approach 1:
The patent defines a universal management mechanism that can handle multiple types of south-side device-specific data (MAC addresses, IP addresses, WWN identifiers, etc.) through a single standardized interface. The SR-PCIM/MR-PCIM provides multi-functional capabilities to manage different device types and data formats without requiring separate management protocols for each device type, thereby improving adaptability while maintaining manageable complexity through standardization.
2Adaptability or versatility
If I/O virtualization is enabled, then resource sharing and scalability are improved, but south-side data management becomes more complex
Solution Approach 1:
The patent segments the management function into distinct components: the SR-PCIM/MR-PCIM handles high-level virtualization and resource allocation, while the south-side management data array handles low-level device-specific data. This segmentation allows I/O virtualization to be implemented without overwhelming complexity in the south-side management layer, as each component has well-defined responsibilities and interfaces.
Solution Approach 2:
The patent introduces the south-side management data array as an intermediary structure between the virtualization layer and the physical device. This intermediary abstracts the complexity of device-specific data management from the virtualization mechanism, allowing I/O virtualization to operate independently of specific device implementations while still accessing south-side data through standardized interfaces.
3Ease of operation
If platform-specific code manages south-side resources, then management flexibility is improved, but portability and standardization are reduced
Solution Approach 1:
The patent establishes standardized parameter definitions and data formats for south-side management data (such as address types, identifier formats, and data structures). Platform-specific code can manipulate these standardized parameters according to local requirements while maintaining compatibility with the universal management interface. This allows flexibility in implementation details while preserving portability through standardization of core data structures and interfaces.
Data Source
AI summary
A hypervisor, during device discovery, has code which can examine the south-side management data structure in an adapter's configuration space and determine the type of device which is being configured. The hypervisor may copy the south-side management data structure to a hardware management console (HMC) and the HMC can populate the data structure with south-side data and then pass the structure to the hypervisor to replace the data structure on the adapter. In another embodiment the hypervisor may copy the data structure to the HMC and the HMC can instruct the hypervisor to fill-in the data structure, a virtual function at a time, with south-side management data associations. The administrator can assign south-side data, such as a MAC address for a virtual instance of an Ethernet device, to LPARs sharing the adapter. Thus, a standard way to manage the south-side data of virtual functions is provided.