memd: don't assume min_filelist_kbytes is constant |
||
Issue descriptionmin_filelist_kbytes is incorrectly treated as a constant, but we change it dynamically when starting/stopping ARC++ and this may have an impact on the memory manager behavior under pressure. We see some of the effects indirectly because "available" will change suddenly. It may be good to detect changes. We probably don't want to poll because of the cost. Possibly memd can be notified via another D-Bus signal.
,
Jan 11
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this. |
||
►
Sign in to add a comment |
||
Comment 1 by semenzato@chromium.org
, Nov 2