New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 716777 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
█ dtor@chromium.org
teravest@chromium.org
sonnyrao@chromium.org
█ igo@chromium.org
█ bccheng@chromium.org
diand...@chromium.org
cylee@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug


Participants' hotlists:
Hotlist-1


Sign in to add a comment

coordinate dynamic setting of min_flielist_kbytes with per-board and per-device settings

Project Member Reported by semenzato@chromium.org, Apr 29 2017 
An upstart script resets min_filelist_kbytes when the ARC++ container starts and stops to fixed values, currently 50 MB and 200 MB (soon to be 100 MB and 400 MB since we're adjusting the kernel so that the value reflects the actual total amount of RAM reserved).

However, the CLs for  issue 713415  have now landed, and they allow per-board (at build time) and per-device (at run-time) override values of the default min_filelist_kbytes setting.  These values will be used at boot time, but when the container starts and stops they will be ignored and replaced by the fixed values from the upstart script.

One possible approach is described (or implied) by this CL.

https://chromium-review.googlesource.com/c/489471/

Comment 1 by semenzato@chromium.org, Apr 29 2017 

However, I feel that we should try to fix this issue differently.  We already know that min_filelist_kbytes doesn't work very well because the total amount of instruction pages can vary a lot when using ARC++.

Comment 2 by cylee@chromium.org, May 2 2017

Cc: cylee@chromium.org

Comment 3 by semenzato@chromium.org, May 8 2017 

REMEMBER: when fixing this, also remove /etc/sysctl.d/10-sysctl-mm.conf in the caroline overlay.
►

Sign in to add a comment