1 |
1026 |
ivang |
@c
|
2 |
|
|
@c COPYRIGHT (c) 1988-2002.
|
3 |
|
|
@c On-Line Applications Research Corporation (OAR).
|
4 |
|
|
@c All rights reserved.
|
5 |
|
|
@c
|
6 |
|
|
@c timeCVME961.t,v 1.10 2002/01/17 21:47:46 joel Exp
|
7 |
|
|
@c
|
8 |
|
|
|
9 |
|
|
@include common/timemac.texi
|
10 |
|
|
@tex
|
11 |
|
|
\global\advance \smallskipamount by -4pt
|
12 |
|
|
@end tex
|
13 |
|
|
|
14 |
|
|
@chapter CVME961 Timing Data
|
15 |
|
|
|
16 |
|
|
NOTE: The CVME961 board used by the RTEMS Project to
|
17 |
|
|
obtain i960CA times is currently broken. The information in
|
18 |
|
|
this chapter was obtained using Release 3.2.1.
|
19 |
|
|
|
20 |
|
|
@section Introduction
|
21 |
|
|
|
22 |
|
|
The timing data for the i960CA version of RTEMS is
|
23 |
|
|
provided along with the target dependent aspects concerning the
|
24 |
|
|
gathering of the timing data. The hardware platform used to
|
25 |
|
|
gather the times is described to give the reader a better
|
26 |
|
|
understanding of each directive time provided. Also, provided
|
27 |
|
|
is a description of the interrupt latency and the context
|
28 |
|
|
switch times as they pertain to the i960CA version of RTEMS.
|
29 |
|
|
|
30 |
|
|
@section Hardware Platform
|
31 |
|
|
|
32 |
|
|
All times reported except for the maximum period
|
33 |
|
|
interrupts are disabled by RTEMS were measured using a Cyclone
|
34 |
|
|
Microsystems CVME961 board. The CVME961 is a 33 Mhz board with
|
35 |
|
|
dynamic RAM which has two wait state dynamic memory (four CPU
|
36 |
|
|
cycles) for read accesses and one wait state (two CPU cycles)
|
37 |
|
|
for write accesses. The Z8536 on a SQUALL SQSIO4 mezzanine
|
38 |
|
|
board was used to measure elapsed time with one-half microsecond
|
39 |
|
|
resolution. All sources of hardware interrupts are disabled,
|
40 |
|
|
although the interrupt level of the i960CA allows all interrupts.
|
41 |
|
|
|
42 |
|
|
The maximum interrupt disable period was measured by
|
43 |
|
|
summing the number of CPU cycles required by each assembly
|
44 |
|
|
language instruction executed while interrupts were disabled.
|
45 |
|
|
Zero wait state memory was assumed. The total CPU cycles
|
46 |
|
|
executed with interrupts disabled, including the instructions to
|
47 |
|
|
disable and enable interrupts, was divided by 33 to simulate a
|
48 |
|
|
i960CA executing at 33 Mhz with zero wait states.
|
49 |
|
|
|
50 |
|
|
@section Interrupt Latency
|
51 |
|
|
|
52 |
|
|
The maximum period with interrupts disabled within
|
53 |
|
|
RTEMS is less than
|
54 |
|
|
RTEMS_MAXIMUM_DISABLE_PERIOD microseconds including the instructions
|
55 |
|
|
which disable and re-enable interrupts. The time required for
|
56 |
|
|
the i960CA to generate an interrupt using the sysctl
|
57 |
|
|
instruction, vectoring to an interrupt handler, and for the
|
58 |
|
|
RTEMS entry overhead before invoking the user's interrupt
|
59 |
|
|
handler are a total of RTEMS_INTR_ENTRY_RETURNS_TO_PREEMPTING_TASK
|
60 |
|
|
microseconds. These combine to yield
|
61 |
|
|
a worst case interrupt latency of less than
|
62 |
|
|
RTEMS_MAXIMUM_DISABLE_PERIOD + RTEMS_INTR_ENTRY_RETURNS_TO_PREEMPTING_TASK
|
63 |
|
|
microseconds. [NOTE: The maximum period with interrupts
|
64 |
|
|
disabled within RTEMS was last calculated for Release
|
65 |
|
|
RTEMS_RELEASE_FOR_MAXIMUM_DISABLE_PERIOD.]
|
66 |
|
|
|
67 |
|
|
It should be noted again that the maximum period with
|
68 |
|
|
interrupts disabled within RTEMS is hand-timed. The interrupt
|
69 |
|
|
vector and entry overhead time was generated on the Cyclone
|
70 |
|
|
CVME961 benchmark platform using the sysctl instruction as the
|
71 |
|
|
interrupt source.
|
72 |
|
|
|
73 |
|
|
@section Context Switch
|
74 |
|
|
|
75 |
|
|
The RTEMS processor context switch time is RTEMS_NO_FP_CONTEXTS
|
76 |
|
|
microseconds on the Cyclone CVME961 benchmark platform. This
|
77 |
|
|
time represents the raw context switch time with no user
|
78 |
|
|
extensions configured. Additional execution time is required
|
79 |
|
|
when a TSWITCH user extension is configured. The use of the
|
80 |
|
|
TSWITCH extension is application dependent. Thus, its execution
|
81 |
|
|
time is not considered part of the base context switch time.
|
82 |
|
|
|
83 |
|
|
The CVME961 has no hardware floating point capability
|
84 |
|
|
and floating point tasks are not supported.
|
85 |
|
|
|
86 |
|
|
The following table summarizes the context switch
|
87 |
|
|
times for the CVME961 benchmark platform:
|
88 |
|
|
|