Transactional Memory Write-Only Atomicity Conflict Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In multi-processor systems, traditional synchronization mechanisms for shared data lead to serialization, limiting concurrency and increasing overhead, while existing hardware and software transactional memory solutions face challenges in managing conflicts and ensuring data integrity across multiple CPU cores.

Innovation Solution

A method and system for performing transactional memory operations in a multi-processor environment by executing instructions in an atomic write-only or read-only mode, where the processor monitors write-set or read-set cache lines, aborts transactions upon conflicts, and suppresses aborts due to read-set conflicts, ensuring data integrity and efficient memory access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional synchronization mechanisms (semaphores, locks) are used for shared data access, then data integrity is ensured, but serialization occurs and concurrency is limited

Engineering Contradiction:
Improvedata integrityVSAvoidconcurrency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts the read-set and write-set tracking functionality from traditional locking mechanisms into separate hardware-managed sets. By monitoring cache line states independently for reads and writes, the system removes the need for serialization through semaphores and locks, allowing multiple threads to access shared data concurrently while maintaining data integrity through conflict detection on write-sets.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the synchronization mechanism into separate read-set and write-set tracking systems. Each cache line is monitored independently with separate state bits for read and write operations. This segmentation allows read operations to proceed without blocking other reads or writes, while write operations are properly serialized only when necessary, improving overall concurrency while maintaining reliability.

Inventive Principle:
Principle #1Segmentation

2Productivity

If finer-grained locking is implemented to improve software scalability, then concurrency increases, but system complexity and error-proneness increase significantly

Engineering Contradiction:
Improvesoftware scalabilityVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements self-service synchronization where the hardware automatically tracks read-sets and write-sets, monitors cache line states, and detects conflicts without requiring software intervention. The processor autonomously manages the complexity of fine-grained locking by maintaining separate state bits for each cache line and automatically serializing write operations when conflicts are detected, freeing software from implementing complex locking protocols.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the mechanical software-based locking system with a hardware-based monitoring system that uses cache line state bits and conflict detection logic implemented in the processor. This substitution eliminates the need for software to manually manage locks, conditions, and signaling, reducing system complexity while maintaining or improving scalability.

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

3Speed

If hardware interconnects operate at current CPU frequencies, then data transfer occurs, but latency is limited by physical chip dimensions and speed of light

Engineering Contradiction:
Improvedata transfer rateVSAvoidinterconnect latency
Core Design Contradiction:
SpeedVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-fetching and pre-validating cache lines into the local cache before they are needed for transactional memory operations. The system anticipates future memory access patterns and prepares data in advance, reducing the need for high-speed interconnect transfers during critical transaction execution and thereby reducing latency imposed by physical interconnect limitations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9971690B2Transactional memory operations with write-only atomicity
Publication Date: 2018.05.15 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US9971690B2 patent drawing
  • US9971690B2 patent drawing
  • US9971690B2 patent drawing

AI summary

Execution of a transaction mode setting instruction causes a computer processor to be in an atomic write-only mode ignoring conflicts to certain read-sets of a transaction during transactional execution. Write-set conflicts may still cause a transactional abort. Absent any aborting, the transaction's execution may complete, by committing transactional stores to memory and updating architecture states.