Kernel-Separated Memory Management for Compressed Page Swapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing memory management solutions require intrusive modifications to kernel code, limiting updates and increasing memory pressure due to frequent data dumping and reading from secondary storage devices.
Innovation Solution
A memory management method that utilizes a memory management engine separate from the kernel, allowing for memory compression and data transfer between storage layers without modifying kernel code, using a call function to synchronize memory control groups and manage memory space efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If data in anonymous pages is dumped into secondary storage when memory pressure is large, then memory pressure is reduced, but kernel code modification is required and service life of secondary storage is reduced
Solution Approach 1:
The patent applies parameter changes by compressing data before storing it in secondary storage, changing the physical state of the data from uncompressed to compressed form. This reduces the storage capacity consumption and extends the service life of the secondary storage device while still effectively reducing memory pressure.
Solution Approach 2:
The patent introduces a memory management engine as an intermediary layer between the kernel and the secondary storage device. This engine handles the compression and management of anonymous page data, avoiding direct kernel modifications while enabling efficient memory pressure management through controlled data transfer to secondary storage.
2Quantity of substance
If kernel code is modified to implement memory management solution, then memory pressure can be reduced by dumping data to secondary storage, but code complexity and difficulty of updates increase
Solution Approach 1:
The patent extracts the memory management functionality from the kernel code and places it in a separate memory management engine. This separation allows the kernel to remain unchanged while the memory management engine handles data compression and transfer operations, reducing kernel code complexity and improving maintainability.
Solution Approach 2:
The memory management engine serves as an intermediary that implements the memory management solution without requiring kernel modifications. It provides a clean interface between the kernel's anonymous pages and the secondary storage system, simplifying the overall system architecture.
3Reliability
If data is frequently read from and written to secondary storage, then memory management is maintained, but service life of secondary storage device is reduced
Solution Approach 1:
The patent applies compression to change the size parameter of the data before storage, reducing the amount of data that needs to be read and written to secondary storage. This decreases the wear on the storage device while maintaining effective memory management through selective compression of anonymous page data.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
This application relates to the field of terminal technologies, and relates to a memory management method, an electronic device, and a storage medium. The method includes: writing the memory management method in a form of software code onto a kernel layer, and separating the software code from kernel code. A kernel may call the software code by using a call function to manage memory space. For example, an anonymous page corresponding to an application is compressed into block space, and a compression page corresponding to the application is dumped into a universal flash storage. In this way, memory pressure can be reduced without modifying the kernel code.