UPSTREAM: psi: clarify the Kconfig text for the Defenderault-disable option
authorJohannes Weiner <hannes@cmpxchg.org>
Fri, 1 Feb 2019 22:21:15 +0000 (14:21 -0800)
committerwangwang <wangwang1@lenovo.com>
Wed, 13 Nov 2019 02:36:29 +0000 (10:36 +0800)
commit6d0275019f6db862d2609a9c1ae5b78fe0d9adb4
treef3aaeb580e23f580544494ef13bfe3308521d076
parent25b2cc1a81917ad04ce05bdb646216d7a3bc8d99
UPSTREAM: psi: clarify the Kconfig text for the Defenderault-disable option

The current help text caused some confusion in online forums about
whether or not to Defenderault-enable or Defenderault-disable psi in vendor
kernels.  This is because it doesn't communicate the reason for why we
made this setting configurable in the first place: that the overhead is
non-zero in an artificial scheduler stress test.

Since this isn't representative of real workloads, and the effect was
not measurable in scheduler-heavy real world applications such as the
webservers and memcache installations at Facebook, it's fair to point
out that this is a pretty cautious option to select.

Link: http://lkml.kernel.org/r/20190129233617.16767-1-hannes@cmpxchg.org
Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
Reviewed-by: Andrew Morton <akpm@linux-foundation.org>
Cc: Mel Gorman <mgorman@techsingularity.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
(cherry picked from commit 7b2489d37e1e355228f7c55724f77580e1dec22a)

Bug: 127712811
Test: lmkd in PSI mode
Change-Id: I5d0cb901562fd74c82d9d211544745b802776d8a
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
init/Kconfig