CN108845872B - Method for implementing software timer for embedded system - Google Patents
Method for implementing software timer for embedded system Download PDFInfo
- Publication number
- CN108845872B CN108845872B CN201810642960.6A CN201810642960A CN108845872B CN 108845872 B CN108845872 B CN 108845872B CN 201810642960 A CN201810642960 A CN 201810642960A CN 108845872 B CN108845872 B CN 108845872B
- Authority
- CN
- China
- Prior art keywords
- timer
- software timer
- software
- expiration time
- embedded system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 34
- 230000004913 activation Effects 0.000 claims abstract description 29
- 238000012545 processing Methods 0.000 claims description 15
- 230000007717 exclusion Effects 0.000 claims description 12
- 230000003213 activating effect Effects 0.000 claims description 7
- 230000008569 process Effects 0.000 abstract description 13
- 230000000737 periodic effect Effects 0.000 abstract description 7
- 230000001174 ascending effect Effects 0.000 abstract description 2
- 238000001994 activation Methods 0.000 description 22
- 241000238876 Acari Species 0.000 description 10
- 230000000694 effects Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000010295 mobile communication Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012163 sequencing technique Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000002618 waking effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4812—Task transfer initiation or dispatching by interrupt, e.g. masked
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Executing Machine-Instructions (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention belongs to the technical field of embedded systems, and discloses a software timer implementation method for an embedded system, wherein the embedded system maintains a global linked list and minimum expiration time, the global linked list is arranged in an ascending order according to the expiration time from software to a timer, the software timer is driven by periodic hardware interruption, the system beat number is updated in an interruption processing program, the minimum expiration time of the system is inquired, and if the minimum expiration time is consistent with the current beat number, the task of the software timer is awakened; after the task of the software timer is awakened, inquiring an activation linked list and sending a message to the task corresponding to the expiration timer; and after receiving the timer expiration message, the task processes the corresponding service. The technical scheme of the invention has the advantages of simple implementation, higher precision and lower system overhead.
Description
Technical Field
The invention relates to the technical field of embedded systems, in particular to a software timer implementation method for an embedded system.
Background
A software timer is an indispensable basic component in an embedded operating system. For upper layer application programs, especially in the field of mobile communications, many services need to be implemented by means of a basic component that is timed by software, for example, a timer is used in a mobile communication protocol to manage data packet timeout, a timer is used in communication equipment to report a timed state, and a timer is used in a network management server to manage user timeout.
The purpose of using the timer is not to periodically execute a task or to execute a task until a specified time. However, the usage scenarios are different, and the implementation considerations for the timer are different.
Generally, the operating system provides a timer interface, but the timer management algorithm provided by the operating system may not be satisfactory in managing large-scale timers. In the process of embedded development, due to the requirement of developing services, a plurality of timers with precision on the millisecond level and small jitter range are required to be provided frequently. Especially in a real-time operating system, a good software timer implementation requires higher precision, less processor overhead, and occupies less memory resources. Therefore, it is important to design an efficient timer function to improve the processing efficiency of the system.
Disclosure of Invention
The embodiment of the application provides a method for implementing a software timer for an embedded system, and solves the problems that the software timer occupies more processor resources and the embedded system has lower processing efficiency in the prior art.
The embodiment of the application provides a method for realizing a software timer for an embedded system, which comprises the following steps:
step 1, a hardware timer periodically generates hardware interrupt, and the hardware interrupt drives a software timer;
step 2, the software timer inquires whether a task of the software timer needs to be awakened;
step 3, if the embedded system needs to be awakened, entering a software timer task processing flow, wherein the software timer task queries an activation linked list of the embedded system and sends a message to an expired timer thread;
and 4, the timer thread receives the message and executes the service.
Preferably, the querying, by the software timer in step 2, whether the software timer task needs to be woken up includes:
step 2.1, acquiring the current total beat number of the embedded system;
step 2.2, acquiring the minimum expiration time of the embedded system;
and 2.3, comparing whether the minimum expiration time is the same as the current total beat number, if so, judging that the software timer task needs to be awakened, otherwise, not awakening the software timer task.
Preferably, the software timer task processing flow in step 3 includes:
step 3.1, acquiring a mutual exclusion lock of the activated linked list;
step 3.2, judging whether the number of nodes in the activation linked list is zero, and if the number of nodes in the activation linked list is zero, executing the step 3.10; otherwise, executing step 3.3;
step 3.3, traversing the activated linked list in sequence;
step 3.4, judging whether the expiration time of the software timer is less than the current total beat number of the embedded system, if so, executing step 3.5; otherwise, executing step 3.8;
step 3.5, recording the task number of the expired timer thread;
step 3.6, inquiring the type of the software timer, and if the software timer is a disposable timer, executing step 3.7; otherwise, executing step 3.4;
step 3.7, removing the software timer from the activation linked list, modifying the state of the software timer into a non-enabled state, and executing the step 3.4;
step 3.8, judging whether the expiration time of the software timer is less than the minimum expiration time of the embedded system, if so, executing step 3.9; otherwise, executing step 3.10;
step 3.9, updating the minimum expiration time of the embedded system;
step 3.10, releasing the mutual exclusion lock of the activated linked list;
step 3.11, sending a message to an expired timer thread;
and 3.12, ending.
Preferably, step 1 further comprises:
step a, establishing a software timer;
and b, activating a software timer.
Preferably, the creating of the software timer of the step a comprises:
step a1, applying for a memory;
step a2, creating a timer node;
step a3, an initialization operation is performed.
Preferably, the activating software timer of the step b comprises:
step b1, acquiring the mutual exclusion lock of the activated linked list;
b2, checking the state of the software timer, if the state is the enabling state, releasing the exclusive lock of the activation linked list, and then executing the step b 8; otherwise, performing step b 3;
step b3, modifying the state of the software timer to an enabling state;
step b4, calculating the expiration time of the software timer;
step b5, inserting a software timer into the activation linked list according to the expiration time;
step b6, releasing the mutual exclusion lock of the activated linked list;
step b7, comparing the expiration time of the software timer with the minimum expiration time of the embedded system, and if the expiration time of the software timer is less than the minimum expiration time of the embedded system, updating the minimum expiration time of the embedded system;
and step b8, ending.
Preferably, the method for implementing the software timer for the embedded system further comprises the following steps:
the decommission software timer includes: and deleting the software timer from the activation linked list or modifying the state of the software timer into a non-enabled state.
Preferably, the method for implementing the software timer for the embedded system further includes deleting the software timer:
the deleting the software timer comprises: and deleting the software timer node and releasing the memory.
One or more technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages:
in the embodiment of the application, a software timer is driven by a periodic hardware interrupt, and when a timer in a system expires, a timer task is awakened. The software timer in the application is driven by hardware interruption, enters a soft interruption processing flow after being driven, inquires whether a user space software timer task needs to be awakened in a soft interruption processing program, if the user space software timer task needs to be awakened, the software timer task is responsible for inquiring an activation linked list of a system, sends a message to a corresponding thread of an expired timer, informs the corresponding thread timer to expire, and executes a corresponding service after the corresponding thread receives the message from the timer. Therefore, when the periodic hardware is interrupted, the software timer is driven, the software timer task is not awakened, the timer task is awakened when the timer in the system expires, and the consumption of the kernel space awakening user space process can be greatly reduced; after the timer expires, the traditional callback function is not executed, a special software timer task sends a message to notify the corresponding task, and each task executes the callback by itself, so that the execution time of the timer task can be reduced. In conclusion, the method and the device can greatly reduce the consumption of the kernel space for waking up the user space process and the execution time of the timer task, so the processing efficiency of the system can be improved.
Drawings
In order to more clearly illustrate the technical solution in the present embodiment, the drawings needed to be used in the description of the embodiment will be briefly introduced below, and it is obvious that the drawings in the following description are one embodiment of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without creative efforts.
Fig. 1 is an overall flowchart of a software timer implementation method for an embedded system according to an embodiment of the present invention;
FIG. 2 is a flow diagram of soft interrupt processing according to an embodiment of the present invention;
FIG. 3 is a flow chart of a timer task in an embodiment of the present invention;
FIG. 4 is a flow chart of activating a timer in an embodiment of the present invention;
fig. 5 is a data structure diagram of a timer according to an embodiment of the present invention.
Detailed Description
In order to better understand the technical solution, the technical solution will be described in detail with reference to the drawings and the specific embodiments.
The user of the software timer firstly needs to create, activate the timer to enable the timer to take effect, and the timer is inserted into the global activation linked list during activation. The active linked list is ordered by the expiration time (absolute time) of the timer.
The software timer is driven by periodical hardware interruption, the system beat number ticks is updated in an interruption processing program, the minimum expiration time of the system is inquired, and if the system beat number ticks is consistent with the current ticks, the fact that the timer expires in the user space is indicated, a software timer task is awakened; after the task of the software timer is awakened, inquiring an activation linked list and sending a message to the task corresponding to the expiration timer; and after receiving the timer expiration message, the task processes the corresponding service.
The embodiment of the invention adopts periodic hardware interruption to drive the timer, and in 4G mobile communication, the embodiment of the invention has hardware interruption of millisecond level, and the embodiment of the invention can be divided into four flows: program initialization flow, kernel processing flow, timer task flow and timer user flow.
The program initialization process is to initialize the number of beats of the system and the minimum expiration time of the system. Both the number of beats in the system and the system minimum expiration time kernel space and user space need to be accessed. In the initialization process, a memory of one page is mapped to a user space through mmap in a kernel module, and the memory kernel space and the user space are shared.
In this block of memory:
and reserving 8 bytes for ticks of the system, wherein the initial value is 0. Ticks is triggered to be increased by one every time 1ms interruption comes; the user space timer user needs to calculate the expiration time of the timer based on this ticks value when activating the timer. This block is written in kernel space and read in user space.
And reserving 8 bytes for the minimum expiration time MinExpire of the system, wherein the initial value is 0 xffffffffffffffffff. It keeps the latest timer expiration time (ticks) in the timer's active linked list. Userspace timer user may need to update the MinExpire when the timer is activated (when the MinExpire is greater than the expiration time of the timer); the MinExpire may also need to be updated when the software timer task traverses the activation linked list; this value needs to be read in the interrupt handler to determine whether a software timer task in user space needs to be triggered. This block is written by user space and read by kernel space.
After the initialization process is completed, the periodic process of the timer is entered, as shown in fig. 1. The periodic flow of the timer includes a kernel processing flow and a timer task flow. In the invention, the software timer is driven by adopting hardware interruption (in mobile communication, millisecond-level hardware interruption, taking 1ms as an example in the text), whether a user space software timer task needs to be awakened or not is inquired in a software interruption processing program, and the software timer task is responsible for inquiring an activation linked list of a system, sending a message to a corresponding thread of an expired timer and informing the expiration of the timer. And the thread receives the timer expiration message and executes corresponding services.
The kernel processing flow is shown in fig. 2, and the specific transfer steps are as follows:
the hardware generates interrupt, and the CPU calls a hardware interrupt processing program;
the interrupt handler calls soft interrupt handling.
Wherein the soft interrupt processing comprises the following substeps:
(1) the kernel program maintains the total beat number (total ticks value) of a system, namely ticks shared by the kernel and the user space in the initialization process. Every time an interrupt arrives, the value is increased by one, and the expiration time of the subsequent timer is all based on the current tick value (the expiration time of the timer is calculated when the timer is activated);
(2) the soft interrupt handler queries the latest expiration time (MinExpire) in all registered timers, and if MinExpire is exactly the current tick value, step 3 is entered; otherwise, entering step 5;
(3) the soft interrupt handler sets MinExpire to 0 xffffffffffffffffff;
(4) awakening a waiting application program thread, namely a timer task, wherein the task is a trigger task of a software timer;
(5) and exiting the soft interrupt processing and waiting for the next hard interrupt to arrive.
Then, the processing flow of the software timer task is entered, as shown in fig. 3, the specific steps are as follows:
(1) the software timer task acquires a mutual exclusion lock of an activation linked list;
(2) the software timer task judges whether the number of nodes in the activation linked list is zero, if so, the step 10 is executed; otherwise, executing step 3;
(3) sequentially traversing the activated linked lists;
(4) judging whether the expiration time of the timer is less than the current ticks of the system, if so, executing the step 5; otherwise, executing step 8;
(5) caching a task number corresponding to the thread of the expiration timer;
(6) inquiring the type of the timer, and if the type of the timer is a one-time timer, executing the step 7; otherwise, executing step 4;
(7) removing the timer from the activation linked list, modifying the state of the timer into a disable state, and executing the step 4;
(8) judging whether the expiration time of the timer is less than the minimum expiration time of the system, if so, executing the step 9; otherwise, executing step 10;
(9) updating a system minimum expiration time;
(10) releasing the mutual exclusion lock of the activated linked list;
(11) sending a message to a task (namely a thread) corresponding to the expiration timer;
(12) and (6) ending.
In the invention, users of the software timer can only be tasks (namely threads), the data structure of the timer is shown in fig. 5, each task can create a plurality of timers, the timers are all hung in a linked list of a task management structure, and the maintenance of the linked list is mainly used for conveniently inquiring the timers created by the tasks; the system maintains a global activation linked list, and timers created by all tasks are added to the linked list once activated.
The use method of the timer user is as follows:
the method comprises the following steps: creating a software timer: applying for a memory, creating a timer node, and initializing each domain, wherein the domains comprise a software timer type (single timing or repeated timing), a period of the software timer, a task number and the like;
step two: activating a software timer: the software timer is activated to take effect, and the activation process is shown in fig. 4 and includes the following steps:
(1) acquiring a mutual exclusion lock of an activation linked list;
(2) checking the state of the timer, and if the state is the enabled state, executing the step 8; otherwise, executing step 3;
(3) modifying the timer state to an enabled state;
(4) calculating an expiration time of the timer;
(5) inserting a timer into an activation linked list according to the expiration time, wherein the linked list is a sequencing linked list and is arranged according to the expiration time of the timer in an ascending order;
(6) releasing the mutual exclusion lock of the activated linked list;
(7) comparing the expiration time of the timer with the system minimum expiration time, and updating the system minimum expiration time if the expiration time of the timer is less than the system minimum expiration time; ensuring that the minimum expiration time maintained in the system must be the minimum expiration time of all timers;
(8) and (6) ending.
After the two steps (step one and step two) are completed, the timer is effective. And after the timer task in the process is awakened by the interrupt processing program, traversing the activation linked list, sending a message to the task corresponding to the expired timer, and informing the expired timer of the task. And after receiving the timer expiration message, the task executes the corresponding service.
Further, if the task does not require a software timer, the following steps may be performed:
releasing the timer: deleting the timer from the activation linked list, modifying the state of the timer into a non-enabled state, and failing the timer; if the timer needs to be validated, it needs to be activated again.
Deleting the timer: and deleting the timer node and releasing the memory.
In specific implementation, the method provided by the invention can realize automatic operation by adopting a software technology.
The implementation method of the software timer for the embedded system provided by the embodiment of the invention at least comprises the following technical effects:
1. the software timer is driven by periodic hardware interruption, but the software timer task is not awakened periodically, and only when the timer in the system expires, the timer task needs to be awakened, so that the consumption of the kernel space awakening user space process is greatly reduced; in addition, the hardware interruption generally has the precision reaching the ms level and has small error, so the precision of the invention is higher;
2. the kernel space and the user space share one memory to maintain the total beat number of the system and the minimum expiration time of the system;
3. when the timer expires, the conventional callback function is not executed, a special software timer task sends a message to notify the corresponding task, and each task executes the callback by itself. Therefore, the execution time of the timer task is reduced, the execution of the expired timers is changed from serial to parallel, otherwise, the situation that the software timer task executes the callback function for too long time and cannot process other expired timers is very likely to occur.
Finally, it should be noted that the above embodiments are only for illustrating the technical solutions of the present invention and not for limiting, and although the present invention has been described in detail with reference to examples, it should be understood by those skilled in the art that modifications or equivalent substitutions may be made on the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, which should be covered by the claims of the present invention.
Claims (7)
1. A software timer implementation method for an embedded system is characterized by comprising the following steps:
step 1, a hardware timer periodically generates hardware interrupt, and the hardware interrupt drives a software timer;
step 2, the software timer inquires whether a task of the software timer needs to be awakened;
step 3, if the embedded system needs to be awakened, entering a software timer task processing flow, wherein the software timer task queries an activation linked list of the embedded system and sends a message to an expired timer thread;
step 4, the timer thread receives the message and executes the service;
wherein, the software timer task processing flow in the step 3 includes:
step 3.1, acquiring a mutual exclusion lock of the activated linked list;
step 3.2, judging whether the number of nodes in the activation linked list is zero, and if the number of nodes in the activation linked list is zero, executing the step 3.10; otherwise, executing step 3.3;
step 3.3, traversing the activated linked list in sequence;
step 3.4, judging whether the expiration time of the software timer is less than the current total beat number of the embedded system, if so, executing step 3.5; otherwise, executing step 3.8;
step 3.5, recording the task number of the expired timer thread;
step 3.6, inquiring the type of the software timer, and if the software timer is a disposable timer, executing step 3.7; otherwise, executing step 3.4;
step 3.7, removing the software timer from the activation linked list, modifying the state of the software timer into a non-enabled state, and executing the step 3.4;
step 3.8, judging whether the expiration time of the software timer is less than the minimum expiration time of the embedded system, if so, executing step 3.9; otherwise, executing step 3.10;
step 3.9, updating the minimum expiration time of the embedded system;
step 3.10, releasing the mutual exclusion lock of the activated linked list;
step 3.11, sending a message to an expired timer thread;
and 3.12, ending.
2. The method as claimed in claim 1, wherein the step 2 of querying whether the software timer task needs to be woken up by the software timer comprises:
step 2.1, acquiring the current total beat number of the embedded system;
step 2.2, acquiring the minimum expiration time of the embedded system;
and 2.3, comparing whether the minimum expiration time is the same as the current total beat number, if so, judging that the software timer task needs to be awakened, otherwise, not awakening the software timer task.
3. The method for implementing the software timer of the embedded system according to claim 1, wherein the step 1 is preceded by:
step a, establishing a software timer;
and b, activating a software timer.
4. The method for implementing the software timer of the embedded system according to claim 3, wherein the creating the software timer of the step a comprises:
step a1, applying for a memory;
step a2, creating a timer node;
step a3, an initialization operation is performed.
5. The software timer implementing method for an embedded system according to claim 3, wherein the activating the software timer of the step b comprises:
step b1, acquiring the mutual exclusion lock of the activated linked list;
b2, checking the state of the software timer, if the state is the enabling state, releasing the exclusive lock of the activation linked list, and then executing the step b 8; otherwise, performing step b 3;
step b3, modifying the state of the software timer to an enabling state;
step b4, calculating the expiration time of the software timer;
step b5, inserting a software timer into the activation linked list according to the expiration time;
step b6, releasing the mutual exclusion lock of the activated linked list;
step b7, comparing the expiration time of the software timer with the minimum expiration time of the embedded system, and if the expiration time of the software timer is less than the minimum expiration time of the embedded system, updating the minimum expiration time of the embedded system;
and step b8, ending.
6. The method for implementing the software timer of the embedded system according to any one of claims 1 to 5, further comprising releasing the software timer:
the decommission software timer includes: and deleting the software timer from the activation linked list or modifying the state of the software timer into a non-enabled state.
7. The method for implementing the software timer of the embedded system according to any one of claims 1 to 5, further comprising deleting the software timer:
the deleting the software timer comprises: and deleting the software timer node and releasing the memory.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810642960.6A CN108845872B (en) | 2018-06-21 | 2018-06-21 | Method for implementing software timer for embedded system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810642960.6A CN108845872B (en) | 2018-06-21 | 2018-06-21 | Method for implementing software timer for embedded system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108845872A CN108845872A (en) | 2018-11-20 |
| CN108845872B true CN108845872B (en) | 2021-02-02 |
Family
ID=64203221
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810642960.6A Active CN108845872B (en) | 2018-06-21 | 2018-06-21 | Method for implementing software timer for embedded system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108845872B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111240815B (en) * | 2020-01-03 | 2023-09-26 | 杭州涂鸦信息技术有限公司 | Infrared signal modulation method and system based on linux |
| CN113835851A (en) * | 2021-08-19 | 2021-12-24 | 威胜信息技术股份有限公司 | Method for implementing real-time operating system timer |
| CN113961273A (en) * | 2021-10-20 | 2022-01-21 | 浙江微度医疗器械有限公司 | Multitask running software timer based on DSP |
| CN115934000B (en) * | 2023-03-07 | 2023-06-09 | 苏州浪潮智能科技有限公司 | Timing method and related device of storage system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1755614A (en) * | 2004-09-29 | 2006-04-05 | 华为技术有限公司 | Timer realizing method |
| CN101221512A (en) * | 2007-01-12 | 2008-07-16 | 中兴通讯股份有限公司 | Timing method and system used for real-time operating system |
| JP2010009434A (en) * | 2008-06-30 | 2010-01-14 | Meidensha Corp | Load distribution method in collection of monitor and control information |
| CN101859260A (en) * | 2010-05-14 | 2010-10-13 | 中国科学院计算技术研究所 | Timer management device and management method used in operating system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8959233B2 (en) * | 2011-02-23 | 2015-02-17 | Hewlett-Packard Development Company, L.P. | Network bottlenecks |
-
2018
- 2018-06-21 CN CN201810642960.6A patent/CN108845872B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1755614A (en) * | 2004-09-29 | 2006-04-05 | 华为技术有限公司 | Timer realizing method |
| CN101221512A (en) * | 2007-01-12 | 2008-07-16 | 中兴通讯股份有限公司 | Timing method and system used for real-time operating system |
| JP2010009434A (en) * | 2008-06-30 | 2010-01-14 | Meidensha Corp | Load distribution method in collection of monitor and control information |
| CN101859260A (en) * | 2010-05-14 | 2010-10-13 | 中国科学院计算技术研究所 | Timer management device and management method used in operating system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108845872A (en) | 2018-11-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108845872B (en) | Method for implementing software timer for embedded system | |
| CN111367679B (en) | Artificial intelligence computing power resource multiplexing method and device | |
| US20080071853A1 (en) | Distributed-leader-election service for a distributed computer system | |
| US20050108385A1 (en) | Method and system for managing a discovery-related process in a network | |
| Cho et al. | Natjam: Design and evaluation of eviction policies for supporting priorities and deadlines in mapreduce clusters | |
| US8495266B2 (en) | Distributed lock | |
| US8270299B2 (en) | Communicator-based token/buffer management for eager protocol support in collective communication operations | |
| US11907762B2 (en) | Resource conservation for containerized systems | |
| US10091307B2 (en) | Application management method and terminal | |
| US20030187907A1 (en) | Distributed control method and apparatus | |
| CN102081557A (en) | Resource management method and system in cloud computing operating system | |
| CN106302700B (en) | Distributed system consistent update method and system based on paxos algorithm | |
| US7310803B2 (en) | Method and system for executing multiple tasks in a task set | |
| CN112445598A (en) | Task scheduling method and device based on quartz, electronic equipment and medium | |
| CN110912990B (en) | Method and related equipment for updating consensus period | |
| CN102420709A (en) | Task scheduling management method and device based on task framework | |
| CN113886049A (en) | Timed task running method and device and computer equipment | |
| CN114816678B (en) | Virtual machine scheduling method, system, equipment and storage medium | |
| CN110362444B (en) | Method and apparatus for error handling in communications between distributed software components | |
| CN104572283B (en) | A kind of method suspended with recovering the operation of MPI concurrent applications | |
| CN108563529A (en) | A kind of method and system of automation re-launching applications | |
| CN110750369B (en) | A distributed node management method and system | |
| CN112084014A (en) | A data processing method, device, equipment and medium | |
| CN110417908A (en) | Internet of Things cloud on-off control method and system | |
| CN111404704B (en) | VNF expansion and contraction method and device, network element and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201027 Address after: 430205 No.1 tanhu 2nd Road, Canglong Island, Jiangxia Economic Development Zone, Wuhan City, Hubei Province Applicant after: Wuhan Hongxin Technology Development Co.,Ltd. Address before: 430073 Hubei province Wuhan Dongxin East Lake high tech Development Zone, Road No. 5 Applicant before: Wuhan Hongxin Telecommunication Technologies Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |