Storage Mapping Page Ownership for Non-Serialized Data Flushing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The mixing of page buffers and physical layer blocks (PLBs) in the same logical mapping pages leads to serialized flushing, causing performance degradation and fragmentation in storage systems, especially when using non-volatile random-access memory (NVRAM) and solid state drive (SSD) persistent storage.

Innovation Solution

Implement a persistent memory organization policy to dynamically allocate page buffers and PLBs into specific mapping pages, optimizing their flushing processes by ensuring they are processed efficiently without serialization, using a combination of NVRAM and SSD storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If page buffers and physical layer blocks are mixed in the same mapping pages, then storage system flexibility is improved, but flushing performance deteriorates due to serialization

Engineering Contradiction:

Improvestorage system flexibilityVSAvoidflushing performance

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent divides mapping pages into separate types: PLB mapping pages for physical layer blocks and page buffer mapping pages for page buffers. This segmentation allows independent flushing processes for each type, eliminating serialization and improving flushing performance while maintaining storage flexibility.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If page buffers and physical layer blocks are mixed in the same mapping pages, then storage system flexibility is improved, but storage utilization deteriorates due to fragmentation

Engineering Contradiction:

Improvestorage system flexibilityVSAvoidstorage utilization

Core Design Contradiction:

Adaptability or versatilityVSLoss of substance

Solution Approach 1:

The patent segments mapping pages into dedicated PLB mapping pages and page buffer mapping pages. This prevents fragmentation by ensuring each mapping page type is used consistently for its intended purpose, improving storage utilization while preserving storage system flexibility.

Inventive Principle:

Principle #1Segmentation

3Reliability

If separate flushing processes are used for page buffers and physical layer blocks, then data integrity is improved, but system complexity increases

Engineering Contradiction:

Improvedata integrityVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies local quality by implementing flushing process differentiation based on mapping page type. PLB mapping pages use one flushing process while page buffer mapping pages use another, allowing data integrity for each type without requiring complex coordination across mixed types, thus managing system complexity.

Inventive Principle:

Principle #3Local quality

Data Source

PatentUS12360917B2System and method for flushing data using mapping page ownership

Publication Date: 2025.07.15 DELL PROD LP

AI summary

A method, computer program product, and computing system for generating a plurality of page buffers from a log memory system of the storage system using a persistent memory organization policy. A plurality of physical layer blocks (PLBs) are generated from the log memory system using the persistent memory organization policy. A set of page buffers are allocated from the plurality of page buffers to a first mapping page of a plurality of mapping pages. A PLB is allocated from the plurality of PLBs to a second mapping page of the plurality of mapping pages. One or more IO requests are processed using one or more of the first mapping page and the second mapping page.