summaryrefslogtreecommitdiff
path: root/mm/kmemcheck.c
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2011-06-22 17:47:03 (GMT)
committerScott Wood <scottwood@freescale.com>2015-02-13 22:20:55 (GMT)
commitd569fcdb758b6bfdb8aed2fd0268f53beb9e89f3 (patch)
tree95019fbd6c58a1bdf832f85c6b374cb3d49367cf /mm/kmemcheck.c
parent3c7be4b423f664f686e311e2843fd0b4222b3c59 (diff)
downloadlinux-fsl-qoriq-d569fcdb758b6bfdb8aed2fd0268f53beb9e89f3.tar.xz
sched: Distangle worker accounting from rqlock
The worker accounting for cpu bound workers is plugged into the core scheduler code and the wakeup code. This is not a hard requirement and can be avoided by keeping track of the state in the workqueue code itself. Keep track of the sleeping state in the worker itself and call the notifier before entering the core scheduler. There might be false positives when the task is woken between that call and actually scheduling, but that's not really different from scheduling and being woken immediately after switching away. There is also no harm from updating nr_running when the task returns from scheduling instead of accounting it in the wakeup code. Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Tejun Heo <tj@kernel.org> Cc: Jens Axboe <axboe@kernel.dk> Cc: Linus Torvalds <torvalds@linux-foundation.org> Link: http://lkml.kernel.org/r/20110622174919.135236139@linutronix.de Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'mm/kmemcheck.c')
0 files changed, 0 insertions, 0 deletions