Chassis Virtual Function Mapping for Modular Server I/O
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing server architectures face challenges in efficiently communicating between modular information handling systems, particularly in managing shared and non-shared resources, leading to latency and complexity in managing I/O operations across multiple systems.
Innovation Solution
A chassis system is configured to receive multiple modular information handling systems, where information handling resources map virtual functions to each system, enabling direct communication between them through these virtual functions, thereby simplifying I/O operations and resource management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single monolithic server architecture is used, then system simplicity is maintained, but I/O resource sharing and modular scalability are limited
Solution Approach 1:
The system is divided into modular blade servers that can be independently configured and managed within a chassis. Each blade server is a separate information handling system that can be hot-swapped, allowing the system to be segmented into functional units that share common I/O resources while maintaining individual operational independence.
Solution Approach 2:
The chassis provides universal I/O resources that can be shared across multiple blade servers. The common I/O bus and shared peripherals allow different blade servers to access the same resources dynamically, making the system multi-functional and adaptable to various configurations without requiring dedicated resources for each server.
2Productivity
If multiple modular information handling systems are implemented in a chassis, then resource sharing and scalability improve, but communication latency and management complexity increase
Solution Approach 1:
A chassis management controller acts as an intermediary between blade servers and shared I/O resources. This mediator manages resource allocation, handles communication routing, and coordinates access to shared peripherals, thereby reducing communication latency by providing direct managed paths rather than requiring complex peer-to-peer negotiations between multiple blade servers.
Solution Approach 2:
The system performs preliminary resource allocation and configuration through the chassis management controller before blade servers need to access shared resources. Virtual device functions are pre-configured and mapped to physical functions in advance, so when blade servers need to communicate or access resources, the pathways are already established, reducing access time and latency.
3Ease of operation
If virtual function mapping is implemented across multiple systems, then I/O operation simplification is achieved, but system configuration complexity increases
Solution Approach 1:
The chassis management controller automatically performs virtual function mapping and resource allocation based on blade server requirements. Instead of requiring manual configuration of virtual device functions for each blade server, the system self-configures the mappings, allowing blade servers to access shared I/O resources through simplified virtual interfaces without complex manual setup.
Solution Approach 2:
The chassis management controller serves as an intermediary that abstracts the complexity of virtual function mapping from blade servers. It handles the complex mappings between virtual device functions and physical functions internally, presenting simplified I/O operations to blade servers while managing the configuration complexity centrally rather than requiring each blade server to handle complex virtualization settings.
Data Source
AI summary
In accordance with embodiments of the present disclosure, a system may include a chassis and an information handling resource disposed in an associated slot of the chassis. The chassis may be configured to receive a plurality of modular information handling systems and a plurality of modular information handling resources, each information handling resource received through a slot in the chassis. The information handling resource may be configured to map a first virtual function to a first modular information handling system received by the chassis, map a second virtual function to a second modular information handling system received by the chassis, and communicate data between the first modular information handling system and the second modular information handling system via the first virtual function and the second virtual function.


