1
0
Fork 0

workqueue: fix trivial typo in Documentation/workqueue.txt

Signed-off-by: Chris Bainbridge <chris.bainbridge@gmail.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
hifive-unleashed-5.1
Chris Bainbridge 2015-05-05 12:49:00 +01:00 committed by Tejun Heo
parent 042f7df15a
commit 6888c6f279
1 changed files with 1 additions and 1 deletions

View File

@ -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: