From 6dcd5a23d28020186a13c498f224c1dcc38d2551 Mon Sep 17 00:00:00 2001
From: John Ogness <john.ogness@linutronix.de>
Date: Fri, 19 Oct 2018 10:52:55 +0206
Subject: 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>
---
 realtime/rt-specialties/pres_rt-specialties_en.tex | 1 +
 1 file changed, 1 insertion(+)

(limited to 'realtime/rt-specialties/pres_rt-specialties_en.tex')

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}
 
-- 
cgit v1.2.3

