On Mon, 10 Jun 2019 16:42:27 +0800 Yafang Shao <laoar.shao@xxxxxxxxx> wrote: > Once the reclaim scanning depth goes too deep, it always mean we are > under memory pressure now. > This behavior should be captured by vmpressure_prio(), which should run > every time when the vmscan's reclaiming priority (scanning depth) > changes. > It's possible the scanning depth goes deep in kswapd reclaim path, > so vmpressure_prio() should be called in this path. > > Signed-off-by: Yafang Shao <laoar.shao@xxxxxxxxx> What effect does this change have upon userspace? Presumably you observed some behaviour(?) and that behaviour was undesirable(?) and the patch changed that behaviour to something else(?) and this new behaviour is better for some reason(?).
