Crash Memory Reservation via Driver Usage Estimation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for reserving memory space for a crash kernel in computing systems often result in either wasteful over-estimation or insufficient memory allocation, leading to inefficient use of resources and potential failure in capturing crash data due to manual estimation based on common configurations.

Innovation Solution

A method and system for automatically estimating and reserving crash memory space for a second kernel based on the actual memory usage of device drivers in the first operational kernel, using a crash memory estimation subsystem that collects and analyzes memory usage data to generate an accurate estimate and configure the reserved memory space accordingly.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual estimation of memory space for crash kernel is used, then ease of operation is improved, but memory allocation precision deteriorates leading to either over-estimation waste or insufficient allocation

Engineering Contradiction:
Improveease of memory reservationVSAvoidmemory space estimation accuracy
Core Design Contradiction:
Ease of operationVSMeasurement precision

Solution Approach 1:

The system automatically determines the memory space requirements for the crash kernel by monitoring actual device driver memory usage in the operational kernel. The crash memory estimation subsystem self-calculates the required reserved memory based on real memory consumption data, eliminating the need for manual estimation while achieving precise allocation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system continuously monitors actual device driver memory usage and uses this feedback to dynamically adjust and refine the estimation of required crash kernel memory space. This feedback loop enables the system to adapt to changing memory consumption patterns and achieve accurate memory reservation.

Inventive Principle:
Principle #23Feedback

2Ease of operation

If default memory size (e.g., 128 MB) is used for crash kernel, then ease of operation is improved, but memory allocation precision deteriorates causing wasteful over-estimation on memory-constrained systems

Engineering Contradiction:
Improveease of memory reservationVSAvoidmemory space utilization efficiency
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

Instead of using a fixed default memory size, the system dynamically changes the memory allocation parameter based on actual device driver memory usage measurements. The reserved memory space is adjusted according to the real consumption patterns observed in the operational kernel, optimizing memory utilization for each specific system configuration.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The memory reservation system transitions from a static default value to a dynamic calculation that adapts to actual system conditions. The crash memory estimation subsystem continuously updates the required memory space based on current device driver memory consumption, enabling flexible and efficient memory allocation.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If user estimates memory size manually, then adaptability to different systems is improved, but reliability of crash data capture deteriorates when estimation is too small

Engineering Contradiction:
Improveadaptability to different system configurationsVSAvoidcrash data capture reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system replaces the manual mechanical estimation process with an automated computational approach. The crash memory estimation subsystem uses software-based monitoring and calculation to determine the exact memory requirements, eliminating human error and ensuring reliable crash data capture while maintaining adaptability to different system configurations.

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

Solution Approach 2:

The system creates a virtual copy or representation of the operational kernel's memory usage patterns to analyze and determine the required crash kernel memory space. By monitoring and replicating the memory consumption behavior of device drivers, the system can accurately predict the needed allocation without manual intervention.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS8862930B2Crash recovery memory reservation based on device drivers for an operational kernel
Publication Date: 2014.10.14 RED HAT INC
  • US8862930B2 patent drawing
  • US8862930B2 patent drawing
  • US8862930B2 patent drawing

AI summary

A computing system stores actual memory usage data in a user memory space. The actual memory usage data represents memory usage of a plurality of device drivers that are loaded by a first kernel. The computing system generates an estimate of memory space to be reserved for a second kernel based on the actual memory usage data for the plurality of device drivers that are loaded by the first kernel and reserves memory space for the second kernel using the estimate.