Jump to: navigation, search

GVP MCP:mpc:controlthreadlevel
 
(7 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
|valid=Can be a number between 0 and 99 inclusive, or choose between: NORMAL, ABOVE_NORMAL, HIGHEST or TIME_CRITICAL.
 
|valid=Can be a number between 0 and 99 inclusive, or choose between: NORMAL, ABOVE_NORMAL, HIGHEST or TIME_CRITICAL.
 
|takeseffect=At start/restart
 
|takeseffect=At start/restart
−
|shortdesc=Specifies the thread priority level for the MPC Control thread. The value can be a numeric value from 0 to 99, with 99 being the highest. Or it can be one of the following enumerated values: - NORMAL - ABOVE_NORMAL - HIGHEST - TIME_CRITICAL If an invalid value is specified, priority is not applied to the thread. Numeric values are applied as follows: On Linux - 0 -> priority 0 with policy SCHED_OTHER All other -> specified priority with policy SCHED_RR On Windows - 0 -> NORMAL priority 1-30 -> ABOVE_NORMAL priority 31-60 -> HIGHEST priority 61-99 -> TIME_CRITICAL priority Enumerated values are applied as follows: On Linux - NORMAL -> priority 0 with policy SCHED_OTHER ABOVE_NORMAL -> priority 20 with policy SCHED_RR HIGHEST -> priority 50 with policy SCHED_RR TIME_CRITICAL -> priority 70 with policy SCHED_RR On Windows - NORMAL -> NORMAL priority ABOVE_NORMAL -> ABOVE_NORMAL priority HIGHEST -> HIGHEST priority TIME_CRITICAL -> TIME_CRITICAL priority
+
|shortdesc=
−
}}
+
 
−
{{DraftOption}}
+
Specifies the thread priority level for the MPC Control thread. The value can be a numeric value from 0 to 99, with 99 being the highest. Or it can be one of the following enumerated values:
 +
- NORMAL
 +
- ABOVE_NORMAL
 +
- HIGHEST
 +
- TIME_CRITICAL
 +
If an invalid value is specified, priority is not applied to the thread.
  
 +
Numeric values are applied as follows:
 +
On Linux -
 +
0 -> priority 0 with policy SCHED_OTHER
 +
All other -> specified priority with policy SCHED_RR
 +
On Windows -
 +
0 -> NORMAL priority
 +
1-30 -> ABOVE_NORMAL priority
 +
31-60 -> HIGHEST priority
 +
61-99 -> TIME_CRITICAL priority
  
 +
Enumerated values are applied as follows:
 +
On Linux -
 +
NORMAL -> priority 0 with policy SCHED_OTHER
 +
ABOVE_NORMAL -> priority 20 with policy SCHED_RR
 +
HIGHEST -> priority 50 with policy SCHED_RR
 +
TIME_CRITICAL -> priority 70 with policy SCHED_RR
 +
On Windows -
 +
NORMAL -> NORMAL priority
 +
ABOVE_NORMAL -> ABOVE_NORMAL priority
 +
HIGHEST -> HIGHEST priority
 +
TIME_CRITICAL -> TIME_CRITICAL priority
  
  
 +
}}
 +
{{DraftOption}}
  
 
{{PubExtended}}
 
{{PubExtended}}
−
 
−
 
−
 
  
 
{{DraftExtended}}
 
{{DraftExtended}}
−
 
−
 
−
 
−
 
  
 
{{OptionCreate
 
{{OptionCreate

Latest revision as of 15:41, June 29, 2020



View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

controlthreadlevel

Default Value: HIGHEST
Valid Values: Can be a number between 0 and 99 inclusive, or choose between: NORMAL, ABOVE_NORMAL, HIGHEST or TIME_CRITICAL.
Changes Take Effect: At start/restart


Specifies the thread priority level for the MPC Control thread. The value can be a numeric value from 0 to 99, with 99 being the highest. Or it can be one of the following enumerated values: - NORMAL - ABOVE_NORMAL - HIGHEST - TIME_CRITICAL If an invalid value is specified, priority is not applied to the thread.

Numeric values are applied as follows: On Linux - 0 -> priority 0 with policy SCHED_OTHER All other -> specified priority with policy SCHED_RR On Windows - 0 -> NORMAL priority 1-30 -> ABOVE_NORMAL priority 31-60 -> HIGHEST priority 61-99 -> TIME_CRITICAL priority

Enumerated values are applied as follows: On Linux - NORMAL -> priority 0 with policy SCHED_OTHER ABOVE_NORMAL -> priority 20 with policy SCHED_RR HIGHEST -> priority 50 with policy SCHED_RR TIME_CRITICAL -> priority 70 with policy SCHED_RR On Windows - NORMAL -> NORMAL priority ABOVE_NORMAL -> ABOVE_NORMAL priority HIGHEST -> HIGHEST priority TIME_CRITICAL -> TIME_CRITICAL priority

Draft Option

No draft option

This page was last edited on June 29, 2020, at 15:41.
Comments or questions about this documentation? Contact us for support!