Read-Write Method Using Registry-Based Policy Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The Linux standard resource lock rwlock sequentially processes read and write operations, leading to long read operation delays when write operations are prioritized, as all read operations must wait for write operations to complete, even if multiple read clients are involved.

Innovation Solution

A read-write method that determines a write policy based on read information stored in a registry, allowing write instructions to be executed in a temporary memory while read operations are ongoing, and writing back data only when all read operations are completed, thereby improving processing efficiency by allowing concurrent read and write operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the Linux standard resource lock rwlock is used to sequentially process read and write operations, then data consistency is maintained, but read operation delay increases significantly when write operations are performed

Engineering Contradiction:
Improvedata consistencyVSAvoidread operation delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the hard disk storage space into multiple independent regions, allowing different read and write operations to occur simultaneously in different regions. This spatial segmentation enables concurrent access to the hard disk, resolving the contradiction between maintaining data consistency and reducing read operation delay.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a registry as an intermediary data structure to track read operation states and determine write policy selection. The registry stores information about ongoing read operations, allowing the system to make informed decisions about whether to allow write operations or select alternative write policies, thus managing the trade-off between data consistency and read performance.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If write operations are performed first using standard rwlock, then all read operations must wait for write completion, resulting in long read delays

Engineering Contradiction:
Improvewrite operation completionVSAvoidread operation waiting time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent implements dynamic write policy selection based on the current state of read operations. The system can switch between different write policies (such as waiting for read completion, performing writes in temporary memory, or allowing concurrent writes in different regions) depending on whether read operations are ongoing, thus dynamically optimizing both write completion and read waiting time.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of write operation behavior by introducing multiple write policies that can be selected based on system state. Instead of a fixed sequential write approach, the system can adjust write behavior parameters (such as whether to wait for reads, use temporary memory, or target different regions) to optimize performance under different conditions.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If multiple read clients are served sequentially by a single write operation, then data consistency is maintained, but overall system throughput decreases

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

By segmenting the hard disk into multiple regions and allowing concurrent read and write operations in different regions, the system can serve multiple read clients simultaneously without compromising data consistency. This increases overall system throughput while maintaining reliability through region-based isolation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent enables continuous useful action by allowing read operations to proceed without being blocked by write operations. Through the use of multiple regions and conditional write policies, the system maintains continuous data flow for both reads and writes, maximizing system throughput while preserving data consistency through proper synchronization mechanisms.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS11868620B2Read-write method and apparatus, electronic device, and readable memory medium
Publication Date: 2024.01.09 INSPUR SUZHOU INTELLIGENT TECH CO LTD
  • US11868620B2 patent drawing
  • US11868620B2 patent drawing
  • US11868620B2 patent drawing

AI summary

Provided are a read-write method and apparatus, an electronic device, and a readable memory medium. The method includes: receiving a write instruction; determining a write policy corresponding to the write instruction according to read information in a registry, wherein the read information is information that, after a read instruction is received, corresponds to the read instruction and is stored in the registry; and executing the write instruction based on the write policy. It can be seen that, according to the present application, a registry is set, read information is registered in the registry when a read instruction is executed, a write policy corresponding to a write instruction is determined according to the read information in the registry before the write instruction is executed, and the write instruction is then executed based on the write policy. Therefore, the read-write processing efficiency is improved.