{"push_id":1348780757,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"e3a6748b1f8be68fa8dd6eca45c6a732d3b810d7","before":"db977d1d504590dcb0557bdbb2f86d56a7399d9d","commits":[{"sha":"e3a6748b1f8be68fa8dd6eca45c6a732d3b810d7","author":{"name":"Vinayak Menon","email":"c6e79b2757471d38dfbeaf17f987a81f42208aac@codeaurora.org"},"message":"mm: vmpressure: scale pressure based on reclaim context\n\nThe existing calculation of vmpressure takes into account only\nthe ratio of reclaimed to scanned pages, but not the time spent\nor the difficulty in reclaiming those pages. For e.g. when there\nare quite a number of file pages in the system, an allocation\nrequest can be satisfied by reclaiming the file pages alone. If\nsuch a reclaim is succesful, the vmpressure value will remain low\nirrespective of the time spent by the reclaim code to free up the\nfile pages. With a feature like lowmemorykiller, killing a task\ncan be faster than reclaiming the file pages alone. So if the\nvmpressure values reflect the reclaim difficulty level, clients\ncan make a decision based on that, for e.g. to kill a task early.\n\nThis patch monitors the number of pages scanned in the direct\nreclaim path and scales the vmpressure level according to that.\n\nSigned-off-by: Vinayak Menon <vinmenon@codeaurora.org>\nChange-Id: I6e643d29a9a1aa0814309253a8b690ad86ec0b13","distinct":true,"url":"https://api.github.com/repos/mawrick26/S6Edge-Alpha/commits/e3a6748b1f8be68fa8dd6eca45c6a732d3b810d7"}]}
{"actor":{"display_login":"mawrick26"}}