Memory Segmentation for Crash Dump Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for managing computing system crashes result in application availability issues, as either the dump process is completed before restarting the system or a minimal startup is initiated, preventing user access until the dump is finished.
Innovation Solution
The system divides the memory into a dumpable and a non-dumpable area, allowing the operating system to reboot using the non-dumpable area while blocking access to the dumpable area until the reboot is complete, then initiating and completing the dump process in parallel with routine operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the dump process is completed before restarting the system, then the system can collect complete crash information, but the system availability is reduced and users cannot access the system during the dump process
Solution Approach 1:
The memory is divided into two separate areas: a dumpable area for crash information collection and a non-dumpable area for system operation. This segmentation allows the dump process and system operations to proceed independently and in parallel, resolving the contradiction between complete information collection and system availability.
2Speed
If a minimal startup is initiated and then the dump is initiated, then the system can start quickly, but user access is prevented until the dump is finished
Solution Approach 1:
By segmenting memory into dumpable and non-dumpable areas, the system enables minimal startup using the non-dumpable area while the dump process operates on the dumpable area. This allows users to access the system immediately after minimal startup without waiting for the dump to complete.
Solution Approach 2:
The system maintains continuous useful action by allowing routine operations to proceed on the non-dumpable area while the dump process simultaneously completes on the dumpable area. This eliminates idle time and ensures continuous system productivity.
3Loss of information
If the entire memory is used for dumping, then complete crash information is collected, but the system cannot perform routine operations during the dump process
Solution Approach 1:
Memory is segmented into dumpable and non-dumpable areas, allowing simultaneous execution of the dump process and routine operations without interference. This resolves the contradiction between complete information collection and continued system productivity.
Solution Approach 2:
The system merges the dump process and routine operations into parallel execution streams by allocating separate memory areas to each, allowing both activities to occur simultaneously and maintain system productivity while collecting crash information.
Data Source
AI summary
A system and a computer program product for managing a computing system crash. Memory of the computing system is separated into at least two classifications, referred to herein as a dumpable area and a non-dumpable area. Upon detection of an operating system crash in the computing system, an operating system module prevents a dumping operation of the memory, including preventing access to the dumpable memory area, and divides the non-dumpable area into a new dumpable area and a new non-dumpable area. At such time as the operating system is rebooted, the dumping operation is initiated and completed in the dumpable area, and resumed operations use the non-dumpable area.