diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2012-12-14 07:20:43 -0800 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2012-12-14 07:20:43 -0800 |
commit | 17bc14b767cf0692420c43dbe5310ae98a5a7836 (patch) | |
tree | 9b0f339e5d9769a51acdeb7a246f6e7522efa966 /arch | |
parent | 7313264b899bbf3988841296265a6e0e8a7b6521 (diff) | |
download | linux-17bc14b767cf0692420c43dbe5310ae98a5a7836.tar.bz2 |
Revert "sched: Update_cfs_shares at period edge"
This reverts commit f269ae0469fc882332bdfb5db15d3c1315fe2a10.
It turns out it causes a very noticeable interactivity regression with
CONFIG_SCHED_AUTOGROUP (test-case: "make -j32" of the kernel in a
terminal window, while scrolling in a browser - the autogrouping means
that the two end up in separate cgroups, and the browser should be
smooth as silk despite the high load).
Says Paul Turner:
"It seems that the update-throttling on the wake-side is reducing the
interactive tasks' ability to preempt. While I suspect the right
longer term answer here is force these updates only in the
cross-cgroup case; this is less trivial. For this release I believe
the right answer is either going to be a revert or restore the updates
on the enqueue-side."
Reported-by: Linus Torvalds <torvalds@linux-foundation.org>
Bisected-by: Mike Galbraith <efault@gmx.de>
Acked-by: Paul Turner <pjt@google.com>
Acked-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions