carlnues@buffalo.edu 2023-08-25 23:02:39 -04:00
commit 56c0af6b18
1 changed files with 0 additions and 4 deletions

View File

@ -86,11 +86,7 @@ We evaluate six different CPU policies under different workloads:
(iv) a truncated \schedutil implemented with \systemname,
(v) unmodified \systemname, and
(vi) the \texttt{performance} governor.
<<<<<<< HEAD
We include (ii) and (iii) to compare the general performance of the truncated \schedutil and a general-case $\sim$70\% speed policies when implemented under the existing API with that when implemented using \systemname.
=======
We include (ii) and (iii) to compare the general performance of the truncated \schedutil and a common-case $\sim$70\% speed policies when implemented under the existing API with the equivalents implemented using \systemname.
>>>>>>> 5a54aecac642577b25bdd5ae50dbe55c0103d47a
Under default Linux, a specific CPU speed requested gets implemented as the next-highest speed in a preset series of supported speeds in \texttt{scaling\_available\_frequencies} in \texttt{sysfs}.
We follow this behavior with our system.