diff options
| author | John Ogness <john.ogness@linutronix.de> | 2018-10-19 10:52:55 +0206 |
|---|---|---|
| committer | John Ogness <john.ogness@linutronix.de> | 2018-10-19 10:48:28 +0200 |
| commit | 6dcd5a23d28020186a13c498f224c1dcc38d2551 (patch) | |
| tree | 194e631fa4611388c139059853d599cc54dd85f8 /realtime | |
| parent | 9e1e6089361d92e6163ab396744a457a05bcccb1 (diff) | |
rt-specialties: add stress-ng as a load scenario
This is how Linutronix was able to reproduce the futex issue.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
Diffstat (limited to 'realtime')
| -rw-r--r-- | realtime/rt-specialties/pres_rt-specialties_en.tex | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/realtime/rt-specialties/pres_rt-specialties_en.tex b/realtime/rt-specialties/pres_rt-specialties_en.tex index ee6b9a4..6fb0fd4 100644 --- a/realtime/rt-specialties/pres_rt-specialties_en.tex +++ b/realtime/rt-specialties/pres_rt-specialties_en.tex @@ -34,6 +34,7 @@ Suitable load scenarios in order to create worst-case situations: \item CPU Load: ''hackbench'', orginally written for scheduler benchmarking \item Interrupt Load: flood pinging (''ping -f'') \item Serial/Network Load: ''top -d 0'' via console and network shell +\item Various Load Scenarios: ''stress-ng'' \end{itemize} \end{frame} |