SLICEMAX parameter: Difference between revisions
Jump to navigation
Jump to search
m (Automatically generated page update) |
(Automatically generated page update) |
||
| Line 17: | Line 17: | ||
<p>SLICEMAX has no effect unless aging is enabled (that is, unless the AGESCAN parameter value is greater than zero). If aging is enabled, SLICEMAX must not be set to less than either CPUSLICE or IOSLICE.</p> | <p>SLICEMAX has no effect unless aging is enabled (that is, unless the AGESCAN parameter value is greater than zero). If aging is enabled, SLICEMAX must not be set to less than either CPUSLICE or IOSLICE.</p> | ||
<p>For more information about <var class="product">Model 204</var> queue aging and dynamic dispatching, see the <var>Model 204 System Manager's Guide</var>. </p> | <p>For more information about <var class="product">Model 204</var> queue aging and dynamic dispatching, see the <var>Model 204 System Manager's Guide</var>. </p> | ||
[[Category: Scheduler | [[Category:Scheduler parameters]] | ||
[[Category: System Parameters]] | [[Category: System Parameters]] | ||
[[Category:Parameters]] | [[Category:Parameters]] | ||
Revision as of 14:12, 19 April 2013
Summary
- Default value
- 0
- Parameter type
- System
- Where set
- On User 0's parameter line or reset by system manager
- Related products
- All
- Introduced
- Model 204 V6.1 or earlier
Description
The maximum CPU time slice in milliseconds that immunity aging can produce
This parameter is used to control the time an aged user remains at the aging-produced priority. Increasing SLICEMAX allows an aged user to monopolize the CPU, possibly locking out high-priority users.
SLICEMAX has no effect unless aging is enabled (that is, unless the AGESCAN parameter value is greater than zero). If aging is enabled, SLICEMAX must not be set to less than either CPUSLICE or IOSLICE.
For more information about Model 204 queue aging and dynamic dispatching, see the Model 204 System Manager's Guide.