It is not obvious how to debug run-away workers.
These are some tips given by Tejun on lkml.
Signed-off-by: Florian Mickler <[email protected]>
Signed-off-by: Tejun Heo <[email protected]>
There are two spellings in use for 'freeze' + 'able' - 'freezable' and
'freezeable'. The former is the more prominent one. The latter is
mostly used by workqueue and in a few other odd places. Unify the
spelling to 'freezable'.
Signed-off-by: Tejun Heo <[email protected]>
Reported-by: Alan Stern <[email protected]>
Acked-by: "Rafael J. Wysocki" <[email protected]>
Acked-by: Greg Kroah-Hartman <[email protected]>
Acked-by: Dmitry Torokhov <[email protected]>
Cc: David Woodhouse <[email protected]>
Cc: Alex Dubov <[email protected]>
Cc: "David S. Miller" <[email protected]>
Cc: Steven Whitehouse <[email protected]>
Add WQ_MEM_RECLAIM flag which currently maps to WQ_RESCUER, mark
WQ_RESCUER as internal and replace all external WQ_RESCUER usages to
WQ_MEM_RECLAIM.
This makes the API users express the intent of the workqueue instead
of indicating the internal mechanism used to guarantee forward
progress. This is also to make it cleaner to add more semantics to
WQ_MEM_RECLAIM. For example, if deemed necessary, memory reclaim
workqueues can be made highpri.
This patch doesn't introduce any functional change.
Signed-off-by: Tejun Heo <[email protected]>
Cc: Jeff Garzik <[email protected]>
Cc: Dave Chinner <[email protected]>
Cc: Steven Whitehouse <[email protected]>
Florian Mickler