summaryrefslogtreecommitdiffstats
path: root/kernel/Documentation/workqueue.txt
diff options
context:
space:
mode:
Diffstat (limited to 'kernel/Documentation/workqueue.txt')
-rw-r--r--kernel/Documentation/workqueue.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/kernel/Documentation/workqueue.txt b/kernel/Documentation/workqueue.txt
index f81a65b54..5e0e05c51 100644
--- a/kernel/Documentation/workqueue.txt
+++ b/kernel/Documentation/workqueue.txt
@@ -365,7 +365,7 @@ root 5674 0.0 0.0 0 0 ? S 12:13 0:00 [kworker/1:0]
If kworkers are going crazy (using too much cpu), there are two types
of possible problems:
- 1. Something beeing scheduled in rapid succession
+ 1. Something being scheduled in rapid succession
2. A single work item that consumes lots of cpu cycles
The first one can be tracked using tracing: