Memory Controller Iterative Write Interruption

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Memory devices with iterative write sequences experience longer write latencies compared to read latencies, causing read operations to wait until write operations are complete, which can adversely affect overall system performance.

Innovation Solution

A memory apparatus with a media controller and read-write engine that tracks the progress of iterative write sequences and determines the optimal time to issue read requests to interrupt the write sequence, aligning with adjacent operations to maintain fixed read latencies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If iterative write sequences are used to ensure reliable data writing, then write reliability is improved, but write latency increases significantly

Engineering Contradiction:
Improvewrite reliabilityVSAvoidwrite latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-charging bitlines and preparing memory banks before the actual write operation. The iterative write sequence includes preliminary read operations to check current data state before applying write voltages, and preliminary verification steps to determine if additional write iterations are needed. This preliminary preparation reduces the overall write latency by avoiding unnecessary operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The write operation uses periodic iterative sequences of write-verify-write cycles. Instead of a single continuous write operation, the system periodically applies write voltages followed by verification reads, repeating this cycle until data is successfully written. This periodic approach ensures reliability while allowing early termination if verification succeeds quickly.

Inventive Principle:
Principle #19Periodic action

2Stability of the object's composition

If read operations wait for iterative write sequences to complete, then data consistency is maintained, but read performance deteriorates

Engineering Contradiction:
Improvedata consistencyVSAvoidread performance
Core Design Contradiction:
Stability of the object's compositionVSProductivity

Solution Approach 1:

The memory system is segmented into multiple independent memory banks that can operate concurrently. When a write operation is initiated to one bank, other banks remain available for read operations. The system tracks the state of each bank individually, allowing reads to proceed in parallel with writes in different banks, thus maintaining data consistency within each bank while improving overall read performance.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A media controller acts as an intermediary between the processor and memory banks, tracking the state of iterative write sequences and managing read-write arbitration. The controller determines whether a read request can be serviced immediately or must wait for write completion, making intelligent decisions to maintain data consistency while minimizing read delays. This intermediary layer abstracts the complexity of write states from the read path.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If memory protocols enforce fixed read and write timings, then interface compatibility is maintained, but flexibility to optimize write operations is reduced

Engineering Contradiction:
Improveinterface compatibilityVSAvoidwrite efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system dynamically adjusts write operation timing and duration based on actual write progress and verification results. While the memory interface maintains fixed timing slots for protocol compliance, the actual write voltage application and verification operations are dynamically controlled - extending only as long as needed based on whether data has been successfully written. This dynamic adaptation improves write efficiency while maintaining interface compatibility.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The iterative write sequence changes physical parameters such as write voltage magnitude and duration across multiple iterations. Each write iteration may use different voltage levels or pulse widths, and the verification step checks if the parameter changes achieved the desired data state. This parameter variation enables reliable writing to high-density memory cells while the overall operation fits within fixed protocol timing constraints.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10671291B2Iterative write sequence interrupt
Publication Date: 2020.06.02 HEWLETT PACKARD ENTERPRISE DEV LP
  • US10671291B2 patent drawing
  • US10671291B2 patent drawing
  • US10671291B2 patent drawing

AI summary

Example implementations relate to memory read requests. For example, an implementation may include tracking progress of an iterative write sequence to write data to a memory element of a memory module. A received read request is detected to be addressed to a memory bank that includes the memory element undergoing the iterative write sequence. Based on the tracked progress, a time is determined to interrupt the iterative write sequence with insertion of the read request. The time aligns between operations of the iterative write sequence and data is returned within a predetermined read latency.