diff options
| author | mattm@chromium.org <mattm@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-08-22 20:53:17 +0000 |
|---|---|---|
| committer | mattm@chromium.org <mattm@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-08-22 20:53:17 +0000 |
| commit | 1dcae06794d4875c9566ffdd5b335594ec3746a0 (patch) | |
| tree | d9c341e873302205cd0854a3c0a02bdac80c2edf /gpu | |
| parent | ab312f8e72b10eb20bdeef6bd79eb36ad995a05b (diff) | |
| download | chromium_src-1dcae06794d4875c9566ffdd5b335594ec3746a0.zip chromium_src-1dcae06794d4875c9566ffdd5b335594ec3746a0.tar.gz chromium_src-1dcae06794d4875c9566ffdd5b335594ec3746a0.tar.bz2 | |
Revert 97724 - Changing OOM range to 0, 1000 and tweaking OOM algorithm.
With this change, we now use the newer oom_score_adj file (with
fallback to oom_adj when on a system that doesn't support it) so that
we can take advantage of a finer range ([0, 1000] instead of [0, 15]).
Also tweaked the OOM priority manager to prioritize things in a
slightly different order, preferring (even more) not to kill tabs that
the user has currently selected.
BUG=chromium-os:18421, chromium:65009
TEST=Ran on device, observed OOM adj values, forced OOM conditions to
watch kills.
Review URL: http://codereview.chromium.org/7671033
TBR=gspencer@google.com
Review URL: http://codereview.chromium.org/7685030
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@97728 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'gpu')
0 files changed, 0 insertions, 0 deletions