Abstract:
PURPOSE: A snapshot storage method and device are provided to store a snapshot in continued blocks of a non-volatile memory, thereby minimizing booting time of a system. CONSTITUTION: A preparation unit(111) prepares a snapshot in a main memory unit. A block assignment unit(112) receives a continuous reference block in a non-volatile memory unit. When the block assignment unit assigns the continuous reference block, a storage unit(113) stores the snapshot in the assigned continuous reference block. A swap table preparation unit(114) prepares storage information of the snapshot in a swap table and stores the same in the non-volatile memory unit. When the block assignment unit does not assign the continuous reference block, the block assignment unit receives variable continuous blocks in the non-volatile memory unit. [Reference numerals] (111) Preparation unit; (112) Block assignment unit; (113) Storage unit; (114) Swap table preparation unit; (121) Storage information acquisition unit; (122) Block lead unit; (123) Restoration unit;
Abstract:
PURPOSE: A tightly-coupled memory management method is provided to improve the response of real-time processes by determining the page to be loaded on the TCM in consideration of a process priority or memory address accessed to TCM, access frequency and recent access time. CONSTITUTION: A process to be saved in a tightly-coupled memory (TCM) requests the access to TCM(210). The TCM transfers the process or the memory information to a TCM manager(220). The process information includes the priority information. The memory information includes the address of the accessed memory, access frequency and recent access time. The TCM manager determines a memory page to be loaded on TCM in consideration of the information on the process or the memory, and then executes the load(230).
Abstract:
The present invention relates to a method and apparatus for scheduling requests having priorities and deadlines for an I/O operation on a disk storage medium. Requests are normally arranged and processed in deadline order, and requests whose process times based on deadlines overlap each other are processed in priority order. Therefore, it is possible to prevent processing of any requests having relatively higher priorities from being delayed due to a process based on deadline order. Further, in order to minimize seek time, the requests may also be processed in the scanning order. Furthermore, in order to minimize a time required for performing request search and arrangement in the scanning order and the deadline order, a deadline queue where requests are arranged in deadline order and a scan order queue where requests are arranged in the scanning order may be separately prepared.