File System Thread Pool Management via Persistent Memory

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current file system management systems face inefficiencies in handling data requests due to limitations in accessing and manipulating data at a byte-level in persistent storage, which requires copying blocks of data to intermediary storage before manipulation, whereas memory allows direct byte-level access.

Innovation Solution

A method that identifies and redirects data requests to appropriate physical devices, leveraging persistent memory to optimize data management by establishing direct virtual-to-physical address mappings, allowing for direct manipulation and optimization of data access within the file system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If block-level access is used in persistent storage, then data can be stored and retrieved, but direct byte-level manipulation is not possible requiring copying to intermediary storage

Engineering Contradiction:
Improvebyte-level data manipulationVSAvoiddata access process
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces persistent memory as an intermediary layer between traditional persistent storage and memory. This persistent memory layer provides byte-level addressability while maintaining non-volatility, allowing direct byte-level manipulation without requiring copying to intermediary storage. The persistent memory acts as a mediator that bridges the gap between block-level persistent storage and byte-level memory access.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the mechanical block-level access system with a persistent memory system that enables direct byte-level addressing. Instead of copying entire data blocks to intermediary storage for manipulation, the system directly accesses and manipulates individual bytes in persistent memory, substituting the traditional mechanical copying process with direct electronic addressing.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Speed

If data is copied to intermediary storage for manipulation, then byte-level access is enabled, but access time and processing efficiency increase

Engineering Contradiction:
Improvedata access speedVSAvoiddata copying time
Core Design Contradiction:
SpeedVSLoss of time

Solution Approach 1:

The patent extracts the copying step from the data access process by using persistent memory that natively supports byte-level addressing. Instead of copying data from persistent storage to intermediary storage for manipulation, the system directly accesses and manipulates data in persistent memory, removing the unnecessary copying operation and its associated time loss.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent enables continuous data manipulation operations in persistent memory without interruption for copying. Data can be read, manipulated, and written back in a continuous flow within the persistent memory layer, eliminating the breaks in the useful action that occur during copy operations between storage layers.

Inventive Principle:
Principle #20Continuity of useful action

3Productivity

If traditional file system management is used, then data can be stored, but direct manipulation without block copying is not possible

Engineering Contradiction:
Improvefile system operation efficiencyVSAvoidstorage access mechanism
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent makes persistent memory serve multiple functions: it acts as both persistent storage and as a directly addressable memory layer for byte-level manipulation. This multi-functionality eliminates the need for separate intermediary storage and manipulation systems, improving file system operation efficiency while managing complexity through a unified persistent memory interface.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11294725B2Method and system for identifying a preferred thread pool associated with a file system
Publication Date: 2022.04.05 EMC IP HLDG CO LLC
  • US11294725B2 patent drawing
  • US11294725B2 patent drawing
  • US11294725B2 patent drawing

AI summary

A method for managing file systems, includes receiving, by a processor coordinator, a first operation request, identifying a file system associated with the first operation request, making a first determination that the file system is local, and in response to the first determination identifying a core thread pool associated with the file system, and directing operation of the first operation request to be executed on a core associated with the core thread pool, wherein the core is associated with a processor.