Task allocation method and device based on shared stack and computer equipment

Abstract

The invention provides a task allocation method for a shared stack, which comprises the following steps: establishing the shared stack, and generating a first task; controlling the first task to run on the shared stack; obtaining preset first heap memory information; backing up stack data of the first task to a first heap memory corresponding to first heap memory information; recovering stack data of a second task to the shared stack, and controlling the second task to run on the shared stack; through the mode of setting the shared stack, the waste degree of the thread stack can be reduced, the unused part of the thread stack can be used as a normal heap memory, the on-chip memory of a chip is compressed, the chip cost is reduced, the memory overhead is reduced, and the space waste of the thread stack is reduced to the maximum extent.

Description

technical field [0001] The present invention relates to the field of communication technologies, and in particular, to a method, device, computer equipment and storage medium for task allocation based on a shared stack. Background technique [0002] Embedded operating systems currently on the market, such as FreeRTOS, RT-Thread, etc., allocate a stack space for each thread when creating a thread to save on-site and temporary variables when the thread is running. like figure 1 As shown, when different threads are running, the SP pointer will be modified to point to the position of the thread stack. [0003] In the existing thread operation mode, the unused part of the thread stack cannot be reused. when the operating system is running figure 1 When TaskC is not identified in , the stacks of TaskA and TaskB are in the figure 1 In the state shown, the free part of the two thread stacks has not been used by the thread, but other threads cannot use this part of the memory, re...

AI Technical Summary

Problems solved by technology

[0003] In the existing thread operation mode, the unused part of the thread stack cannot be reused

when the operating system is running figure 1 When TaskC is not identified in , the stacks of TaskA and TaskB are as follows figure 1 In the state shown, the free part of the two thread stacks has not been used by the thread, but other threads cannot use this part of memory, resulting in memory waste

Secondly, it is difficult to set the size of the thread stack. If you want to save memory as much as possible, you need to ensure that after the thread runs, the maximum stack space used by the thread just reaches the allocated stack space, but even after sufficient testing, it is not guaranteed. The maximum stack space usage obtained is the value obtained by the test, and a certain margin needs to be left. Moreover, adding some operation codes or function calls at will may change the usage of the stack space, and allocate as much as possible for the stack space. Small values ​​make it very difficult to

Images