After commit 839a8e86("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 somewhat userland visible
and we won't be exposing exactly the same information with just a different
name.Signed-off-by: Wanpeng Li <[email protected]> --- include/linux/writeback.h | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/include/linux/writeback.h b/include/linux/writeback.h index 8b5cec4..ac73a9d 100644 --- a/include/linux/writeback.h +++ b/include/linux/writeback.h @@ -47,6 +47,11 @@ 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 somewhat userland visible and we'll be exposing + * exactly the same information, so it has a mismatch name. + */ WB_REASON_FORKER_THREAD, WB_REASON_MAX, -- 1.7.5.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
