Network Hardware User Manual

446 U3585-J-Z125-8-76
Glossary
An SDV rejected in SDV fast release mode is ignored; this also results in an increase in
waiting time for the device.
In "offline seek" mode, the time between the first SDV and the termination message for
the second SDV is counted.
CPU time and CPU service units on SR2000
On SR2000 systems, the CPU time consumed depends on whether the code is
executed in /390 mode (compatibility mode) under the /390 firmware or in RISC mode
directly on the RISC CPU. The higher the proportion of code in /390 mode compared to
the proportion of code in RISC mode, the greater the consumption of (native) CPU time.
The following values describe the CPU time and CPU service units on SR2000
systems:
deactivation, forced deactivation
When a task is deactivated, it is no longer authorized to use the CPU. In the case of
forced deactivation, the system withdraws the task’s right to use the CPU.
Forced deactivation can occur when resources are extremely overloaded.
(Native) task CPU
time
As before, this represents the RISC CPU time consumed by the
task. This consists of the /390 CPU time and the time during
which the task is executed directly on the CPU in RISC mode.
/390 CPU time This is the time during which a task is executed on the RISC
CPU under the control of the /390 firmware (in /390 mode). This
arises only in the TU state. The /390 CPU time of a task is a
subset of the native task CPU time.
(Native) CPU
service units
As before, this specifies the weighted load of the CPU.
Standardized CPU
time
This maps the (native) CPU time consumed on the RISC system
to the task CPU time of a /390 system with the same capacity.
The standardized CPU time is not recorded by SM2.
Standardized CPU
service units
This maps the CPU time consumed on the RISC system to the
CPU service units of a /390 system with the same capacity. The
standardized CPU service units are not recorded by SM2.