Storage Class Memory Block Release via EADM Interface

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computing environments face challenges in efficiently managing storage class memory, particularly in releasing blocks of storage class memory and transferring data between main storage and storage class memory, due to complexities in addressing and access times.

Innovation Solution

The implementation of an Extended Asynchronous Data Mover (EADM) Facility, which allows programs to request data transfers and operations between main storage and storage class memory, including releasing blocks of storage class memory, using a standardized channel programming interface that hides the implementation details and provides a method for the program to specify the release of storage class memory blocks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If storage class memory is implemented as groups of solid state devices connected via I/O adapters, then faster access than DASD is achieved, but device complexity increases due to multiple adapters and mapping layers

Engineering Contradiction:
Improveaccess speedVSAvoiddevice complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent introduces an I/O adapter as an intermediary component that bridges storage class memory devices and the system bus. The adapter handles complex mapping and translation functions, isolating the complexity from the main system while enabling fast access to storage class memory through standardized interfaces.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If a standardized channel programming interface is implemented to hide implementation details, then ease of operation improves, but device complexity increases due to additional abstraction layers

Engineering Contradiction:
Improveease of operationVSAvoiddevice complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the storage management system into distinct functional layers: a standardized channel programming interface for user programs, an operation block layer for processing requests, and move specification blocks for detailed data transfer control. This segmentation allows each layer to handle specific tasks independently, simplifying the interface while managing complexity internally.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces operation blocks and move specification blocks as intermediary data structures that translate high-level programming interface requests into low-level storage operations. These intermediaries buffer the complexity of storage class memory management from user programs, providing an easy-to-use interface while enabling sophisticated storage operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If asynchronous data movement is implemented between main storage and storage class memory, then productivity improves, but device complexity increases due to additional control mechanisms

Engineering Contradiction:
ImproveproductivityVSAvoiddevice complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements asynchronous data movement by making the data transfer process dynamic and event-driven rather than synchronous and blocking. Move specification blocks enable data transfers to be initiated and completed independently, with the system dynamically handling multiple operations concurrently, thereby improving productivity while managing complexity through structured control blocks.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9058245B2Releasing blocks of storage class memory
Publication Date: 2015.06.16 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US9058245B2 patent drawing
  • US9058245B2 patent drawing
  • US9058245B2 patent drawing

AI summary

An abstraction for storage class memory is provided that hides the details of the implementation of storage class memory from a program, and provides a standard channel programming interface for performing certain actions, such as controlling movement of data between main storage and storage class memory or managing storage class memory.