Efficient priority-aware thread scheduling
US-2017228260-A1 · Aug 10, 2017 · US
US2016299550A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016299550-A1 |
| Application number | US-201415102459-A |
| Country | US |
| Kind code | A1 |
| Filing date | Dec 4, 2014 |
| Priority date | Dec 10, 2013 |
| Publication date | Oct 13, 2016 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A task management method and device where the method may include determining, according to a foreground task, a first scenario corresponding to the foreground task, searching for at least one background task corresponding to the first scenario, when the first scenario corresponding to the foreground task is in a first list, where the first list includes a scenario in which task limitation is allowed, and performing limitation processing on the at least one background task corresponding to the first scenario, where the limitation processing refers to processing for reducing system resource usage, and the method may reduce power consumption and power loss of a device.
Opening claim text (preview).
1 . A task management method, comprising: determining, according to a foreground task, a first scenario corresponding to the foreground task; searching for at least one background task corresponding to the first scenario, when the first scenario corresponding to the foreground task is in a first list, wherein the first list comprises a scenario in which task limitation is allowed; and performing limitation processing on the background task corresponding to the first scenario, wherein the limitation processing refers to processing for reducing system resource usage. 2 . The method according to claim 1 , comprising: searching for a second scenario except the first scenario corresponding to the foreground task, wherein the second scenario corresponds to at least one background task, and wherein the first list comprises the second scenario; and performing the limitation processing on the background task corresponding to the second scenario. 3 . The method according to claim 1 , wherein after determining, according to the foreground task, the first scenario corresponding to the foreground task, the method further comprises: determining whether the first scenario is in the first list. 4 . The method according to claim 1 , wherein before performing the limitation processing on the at least one background task corresponding to the first scenario, the method further comprises: querying a user identifier of the background task; ignoring the at least one background task when the user identifier of the background task corresponds to a system user; and performing the limitation processing on the background task when the user identifier of the background task corresponds to a common user. 5 . The method according to claim 1 , wherein before performing the limitation processing on the at least one background task corresponding to the first scenario, the method further comprises: starting a timer for the background task corresponding to the first scenario; and stopping a system component used by the background task corresponding to the first scenario when the timer exceeds a preset threshold. 6 . The method according to claim 1 , wherein before performing the limitation processing on the at least one background task corresponding to the first scenario, the method further comprises: querying whether the background task uses a system component; and stopping the system component when the background task uses the system component. 7 . The method according to claim 1 , wherein processing for reducing the system resource usage comprises at least one of the following manners: freezing the at least one background task; stopping the background task; and limiting a system resource used by the background task. 8 . The method according to claim 1 , wherein determining, according to the foreground task, the first scenario corresponding to the foreground task comprises determining, according to at least one foreground task, the first scenario corresponding to each of the foreground task. 9 . A task management method, comprising: determining, according to a foreground task, a first scenario corresponding to the foreground task; determining a second scenario except the first scenario corresponding to the foreground task, wherein the second scenario is a scenario in which task limitation is allowed, and wherein the second scenario corresponds to at least one background task; searching for the background task corresponding to the second scenario; and performing limitation processing on the background task corresponding to the second scenario, wherein the limitation processing refers to processing for reducing system resource usage. 10 . The method according to claim 9 , further comprising: searching for at least one background task corresponding to the first scenario; and performing the limitation processing on the background task corresponding to the first scenario when a user identifier of the background task corresponding to the first scenario corresponds to a common user. 11 . The method according to claim 9 , wherein before performing the limitation processing on the at least one background task corresponding to the second scenario, the method further comprises: starting a timer for the background task corresponding to the second scenario; and stopping a system component used by the background task corresponding to the second scenario when the timer exceeds a preset threshold. 12 . The method according to claim 9 , wherein before performing the limitation processing on the at least one background task corresponding to the second scenario, the method further comprises: querying whether the background task uses a system component; and stopping the system component when the background task uses the system component. 13 . The method according to claim 9 , wherein processing for reducing the system resource usage comprises at least one of the following manners: freezing the background task; stopping the at least one background task; and limiting a system resource used by the background task. 14 . The method according to claim 9 , wherein determining, according to the foreground task, the first scenario corresponding to the foreground task comprises determining, according to at least one foreground task, the first scenario corresponding to each of the foreground task. 15 .- 22 . (canceled) 23 . A task management device, comprising: a memory; and a processor coupled to the memory and configured to: determine, according to a foreground task, a first scenario corresponding to the foreground task; determine a second scenario except the first scenario that corresponds to the foreground task, wherein the second scenario is a scenario in which task limitation is allowed and corresponds to at least one background task; search for the background task corresponding to the second scenario; and perform limitation processing on the background task that corresponds to the second scenario, wherein the limitation processing refers to processing for reducing system resource usage. 24 . The device according to claim 23 , wherein the processor is further configured to: search for at least one background task corresponding to the first scenario; and perform the limitation processing on the background task corresponding to the first scenario when a user identifier of the background task corresponding to the first scenario corresponds to a common user. 25 . The device according to claim 23 , wherein the processor is further configured to: start a timer for the at least one background task corresponding to the second scenario; and a system component used by the background task corresponding to the second scenario when the timer exceeds a preset threshold. 26 . The device according to claim 23 , wherein the processor is further configured to: query whether the at least one background task uses a system component; and stop the system component when the background task uses the system component. 27 . The device according to claim 23 , wherein processing for reducing the system resource usage comprises at least one of the following manners: freezing the at least one background task; stopping the background task; and limiting a system resource used by the background task. 28 . The device according to claim 23 , wherein the processor is further configured to determine, according to at least one foreground task, the first scenario corresponding to each foreground
Monitoring task completion, e.g. by use of idle timers, stop commands or wait commands · CPC title
where the allocation takes into account power or heat criteria (power management in computers in general G06F1/3203; thermal management in computers in general G06F1/206) · CPC title
by task scheduling · CPC title
by switching off individual functional units in the computer system · CPC title
Mechanisms to release resources · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.