Dynamic RSS Engine Migration for VM Packet Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In software-defined networking (SDN) environments, managing the RSS engine states of virtual machines (VMs) to optimize packet processing efficiency is challenging due to limited resources and varying traffic loads, leading to potential latency and inefficient use of PNIC RSS engines.
Innovation Solution
Implementing a method for dynamic migration of VMs between RSS engine states based on monitored traffic loads, allowing the hypervisor to switch VMs between no RSS, shared, and dedicated RSS engine states to optimize resource utilization and improve packet processing efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If VMs are assigned to dedicated RSS engines, then packet processing efficiency is improved, but resource utilization efficiency deteriorates due to limited PNIC RSS engine availability
Solution Approach 1:
The patent implements dynamic migration of VMs between shared and dedicated RSS engine states based on real-time traffic load monitoring. VMs can transition from shared to dedicated state when high packet processing efficiency is needed, and back to shared state when resource constraints require consolidation, making the RSS engine allocation adaptive and flexible
Solution Approach 2:
The system changes the operational parameters of RSS engine allocation by switching between shared and dedicated modes. This parameter change allows the system to optimize between processing efficiency and resource utilization efficiency, resolving the contradiction between these two objectives
2Adaptability or versatility
If VMs are assigned to shared RSS engines, then resource utilization efficiency is improved, but packet processing latency increases due to resource contention
Solution Approach 1:
The system continuously monitors traffic load parameters of VMs and uses this feedback to dynamically adjust RSS engine assignments. When latency becomes problematic due to shared engine contention, the system detects this through traffic load monitoring and migrates affected VMs to dedicated engines, thereby reducing latency while maintaining efficient resource utilization overall
3Device complexity
If static RSS engine assignment is used, then system complexity is reduced, but adaptability to changing traffic loads deteriorates
Solution Approach 1:
The system implements self-service through automated hypervisor-driven migration. The hypervisor autonomously monitors traffic loads, evaluates RSS engine states, and executes VM migrations between shared and dedicated states without manual intervention. This automation manages the complexity of dynamic adaptation while maintaining low operational overhead
Data Source
AI summary
Systems and methods for dynamic migration between Receive Side Scaling (RSS) engine states include monitoring a traffic load of a first shared RSS engine of a physical network interface card (PNIC) of a host machine, the first shared RSS engine being shared among a first plurality of virtual machines (VMs) running on the host machine, determining the traffic load of the first shared RSS engine exceeds a threshold, and, in response to determining that the traffic load of the first shared RSS engine exceeds the threshold, migrating a first VM of the first plurality of VMs to either a dedicated RSS engine of the PNIC or to a second shared RSS engine of the PNIC.