diff options
| author |   Chris Bainbridge <chris.bainbridge@gmail.com> | 2015-05-05 12:49:00 +0100 |
|---|---|---|
| committer |   Tejun Heo <tj@kernel.org> | 2015-05-05 09:50:38 -0400 |
| commit | 6888c6f279a742a3190e186f44de70951b3491fd (patch) | |
| tree | c98819b34d7bd51f01ce65e886f8202483cdc17a /Documentation/workqueue.txt | |
| parent | workqueue: Allow modifying low level unbound workqueue cpumask (diff) | |
| download | linux-dev-6888c6f279a742a3190e186f44de70951b3491fd.tar.xz linux-dev-6888c6f279a742a3190e186f44de70951b3491fd.zip | |
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>
Diffstat (limited to 'Documentation/workqueue.txt')
| -rw-r--r-- | Documentation/workqueue.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/workqueue.txt b/Documentation/workqueue.txt index f81a65b54c29..5e0e05c5183e 100644 --- a/Documentation/workqueue.txt +++ b/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: |