Processor cache affinity parameters
Parameter
|
Dflt
|
Min
|
Max
|
LOAD_BAL_FREQ
|
100
|
1
|
10000
|
MAXCACHEWARM
|
30
|
0
|
5000
|
MAXIMBALANCE
|
5
|
0
|
100
|
OVSTACK_PREEMPT
|
0
|
0
|
1
|
OVSTACK_SIZE
|
20
|
1
|
0x1000
|
LOAD_BAL_FREQ-
The frequency in ticks with which the lengths of the per-processor run queues
are examined to check that the differences exceed MAXIMBALANCE.
MAXCACHEWARM-
Maximum number of ticks after which the cache is assumed to have turned cold.
MAXIMBALANCE-
The maximum difference between two local run queues that is allowed.
Once this maximum is exceeded, load balancing requirements will dictate
putting affinitized LWPs on global run queue.
OVSTACK_PREEMPT-
A boolean value that controls whether preemption is enabled while a kernel
LWP's (lightweight process's) stack is using the extension page.
When this tunable is set to ``0'' (the default), the
kernel will not preempt an LWP whose stack extends into the
extension page.
When set to ``1'', such preemption is enabled, thereby providing
enhanced real time response.
Enabling this feature can cause increased use of
the stack overflow memory, and
therefore, an increased value of OVSTACK_SIZE is recommended.
OVSTACK_PREEMPT and OVSTACK_SIZE are important when
you use drivers
that use more stack space and when you run real-time applications.
OVSTACK_SIZE-
The quantity of memory (in kilobytes) set aside to handle stack overflow
conditions.
OVSTACK_PREEMPT and OVSTACK_SIZE are important when
you use drivers that use more stack space and when you run real-time
applications.
Next topic:
Security parameters
Previous topic:
Resource limit (rlimit) parameters
© 2007 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 05 June 2007