blob: 638cd758e590d595a4e7de662a2e5eabe0b4b21c (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
|
SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause
appl-config-option-type: integer
copyrights:
- Copyright (C) 1988, 2008 On-Line Applications Research Corporation (OAR)
default-value: 10000
description: |
The value of this configuration option defines the length of time in
microseconds between clock ticks (clock tick quantum).
When the clock tick quantum value is too low, the system will spend so much
time processing clock ticks that it does not have processing time available
to perform application work. In this case, the system will become
unresponsive.
The lowest practical time quantum varies widely based upon the speed of the
target hardware and the architectural overhead associated with
interrupts. In general terms, you do not want to configure it lower than is
needed for the application.
The clock tick quantum should be selected such that it all blocking and
delay times in the application are evenly divisible by it. Otherwise,
rounding errors will be introduced which may negatively impact the
application.
enabled-by: true
index-entries:
- clock tick quantum
- tick quantum
interface-type: appl-config-option
links:
- role: interface-placement
uid: domain
- role: interface-ingroup
uid: group-general
- role: constraint
uid: ../constraint/min-clock-ticks
- role: constraint
uid: ../constraint/max-clock-ticks
- role: constraint
uid: ../constraint/clock-ticks-per-second
name: CONFIGURE_MICROSECONDS_PER_TICK
notes: |
This configuration option has no impact if the Clock Driver is not
configured, see ${appl-does-not-need-clock-driver:/name}.
There may be Clock Driver specific limits on the resolution or maximum value
of a clock tick quantum.
type: interface
|
