Dynamic resource recovery method and system

Abstract

The invention provides a dynamic resource recovery method and system. The method comprises: creating an active chain table and an inactive chain table of shared resources; creating a resource recovery thread and registering a deletion interface of the shared resources to the resource recovery thread; when deleting the shared resources by a thread, moving the shared resources to the inactive chain table from the active chain table, and sending a notification message to the resource recovery thread; and after receiving the notification message by the resource recovery thread, deleting the shared resources in the inactive chain table through the resource recovery thread. According to the method and the system, the resource conflict can be reduced as far as possible and the access risk of other threads caused by false deletion of the resources by certain thread is avoided.

Description

technical field [0001] The invention relates to the field of computer technology, in particular to a method and system for dynamically reclaiming resources. Background technique [0002] Multithreading is a very "thrifty" way of multitasking. Under the Linux system, starting a new process must assign it an independent address space, and establish numerous data tables to maintain its code segment, stack segment and data segment, which is an "expensive" multitasking way of working. However, multiple threads running in one process use the same address space with each other and share most of the resources. It takes much less space to start one thread than to start one process, and the threads switch between each other. The time required is also much less than the time required to switch between processes. Moreover, since the data space is shared between threads under the same process, the data of one thread can be directly used by other threads, which is not only fast but also...

AI Technical Summary

Problems solved by technology

[0007] However, in a multi-threaded program under the Linux system, there is a competitive relationship between various resources. When a thread occupies a certain resource, other resources cannot own the resource. If you want to own it, you usually have to wait for the resource to be released.

When a thread in the system needs to delete certain resources, the resource may be being used by other threads, resulting in that the resource cannot be deleted, and the thread has been waiting for the resource to be released, which actually causes waste

Images