Memory Hypervisor Bypasses Storage Stack for Distributed Node Provisioning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems face performance bottlenecks in handling large data volumes due to inefficient data reading and writing processes, particularly in how applications interact with memory and storage devices, leading to suboptimal performance and scalability.

Innovation Solution

The implementation of a system that allows applications to directly issue I/O requests to storage pools via a memory hypervisor module, bypassing the storage stack, using POSIX interfaces and scale-out volume offsets to manage data layouts and mappings between virtual and physical addresses, enabling transparent interaction with memory devices at scale.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If applications interact with storage through traditional storage stack, then data access is simplified, but performance bottlenecks occur due to inefficient data reading and writing processes

Engineering Contradiction:
Improvedata access performanceVSAvoidstorage interaction complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent extracts the memory hypervisor module from the traditional storage stack architecture. This module is positioned between the application layer and the storage layer, allowing applications to issue I/O requests directly to storage pools without going through the conventional storage stack processing path, thereby improving data access performance while maintaining simplified interaction through POSIX interfaces

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The memory hypervisor module acts as an intermediary component that mediates between applications and storage pools. It receives I/O requests from applications, translates them into appropriate storage operations using scale-out volume offsets, and manages data layouts, thereby enabling direct high-performance access while abstracting the complexity of storage management

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If traditional storage stack is used, then configuration management is maintained, but scalability is limited due to overhead

Engineering Contradiction:
Improvesystem scalabilityVSAvoidprocessing overhead
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent segments the storage access path into distinct functional components: the memory hypervisor module handles I/O request processing and translation, while the storage pools manage actual data storage. This segmentation allows thousands of client application nodes to access storage independently and efficiently, improving system scalability by reducing the overhead on centralized storage stack components

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system employs dynamic configuration management where the memory hypervisor module can adaptively handle I/O requests and manage data layouts based on runtime conditions. The use of scale-out volume offsets enables flexible mapping between virtual and physical addresses, allowing the system to scale dynamically without rigid configuration constraints

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS12007942B2Methods and systems for seamlessly provisioning client application nodes in a distributed system
Publication Date: 2024.06.11 EMC IP HLDG CO LLC
  • US12007942B2 patent drawing
  • US12007942B2 patent drawing
  • US12007942B2 patent drawing

AI summary

In general, embodiment relate to a method for provisioning a plurality of client application nodes in a distributed system using a management node, the method comprising: creating a file system in a namespace; associating the file system with a scale out volume; mounting the file system on a metadata node in the distributed system, wherein mounting the file system comprises storing a scale out volume record of the scale out volume; storing file system information for the file system in a second file system on the management node, wherein the file system information specifies the file system and the metadata node on which the file system is mounted; wherein storing the file system information triggers distribution of the file system information to at least a portion of a plurality of client application nodes.