mm/writeback: commit reason of WB_REASON_FORKER_THREAD mismatch name
authorWanpeng Li <liwanp@linux.vnet.ibm.com>
Mon, 8 Jul 2013 23:00:15 +0000 (16:00 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Tue, 9 Jul 2013 17:33:22 +0000 (10:33 -0700)
After commit 839a8e8660b6 ("writeback: replace custom worker pool
implementation with unbound workqueue"), there is no bdi forker thread
any more.  However, WB_REASON_FORKER_THREAD is still used due to it is
TPs userland visible and we won't be exposing exactly the same
information with just a different name.

Signed-off-by: Wanpeng Li <liwanp@linux.vnet.ibm.com>
Reviewed-by: Tejun Heo <tj@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
include/linux/writeback.h

index e1703ded543aed7b2e52fda3ca97c3b99c66cfc0..4e198ca1f685de549b38ced1644d2b2008d18624 100644 (file)
@@ -47,6 +47,12 @@ enum wb_reason {
        WB_REASON_LAPTOP_TIMER,
        WB_REASON_FREE_MORE_MEM,
        WB_REASON_FS_FREE_SPACE,
+       /*
+        * There is no bdi forker thread any more and works are done
+        * by emergency worker, however, this is TPs userland visible
+        * and we'll be exposing exactly the same information,
+        * so it has a mismatch name.
+        */
        WB_REASON_FORKER_THREAD,
 
        WB_REASON_MAX,