diff options
| author | Wilrik de Loose <wilrik@wilrik.nl> | 2008-05-20 12:47:04 (GMT) |
|---|---|---|
| committer | Wilrik de Loose <wilrik@wilrik.nl> | 2008-05-20 12:47:04 (GMT) |
| commit | b682464751091887cb0c011a5d5ed996716e43b9 (patch) | |
| tree | 61fcae5d18c8dee95444b3b91940a61b11e7cf0c /report/chapter2.tex | |
| parent | 1de84e6d6de7a9f2239deb7245b573ee07067554 (diff) | |
| download | 2in25-b682464751091887cb0c011a5d5ed996716e43b9.zip 2in25-b682464751091887cb0c011a5d5ed996716e43b9.tar.gz 2in25-b682464751091887cb0c011a5d5ed996716e43b9.tar.bz2 | |
+ application domains
Diffstat (limited to 'report/chapter2.tex')
| -rw-r--r-- | report/chapter2.tex | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/report/chapter2.tex b/report/chapter2.tex index 754a33e..f7d5ce0 100644 --- a/report/chapter2.tex +++ b/report/chapter2.tex @@ -7,9 +7,7 @@ Another solution to this problem is to use Fixed Priority Scheduling with Deferr Let us first define two terms now. First, an active cache line is defined in \cite{sp-pppcbrts-95} as a cache line that that contains a block of data that will be referenced in the future prior to its replacement. In other words, it is a cache line in which the next reference is a hit, had the task been allowed to run to completion.
Secondly, a preferred preemption point for a given task interval $ t_i $ to $ t_j $ is defined in \cite{sp-pppcbrts-95} as the instant within the interval having the minimum number of live cache lines. \\
-% ??????
Bearing these in mind, the task we have at hand is to search for the preferred preemption points. There are two main ways that these points can be determined, using a compiler or manually. \\
-% ??????
\subsection{Using a compiler}
|