On Sun 05-02-17 11:11:13, Michal Hocko wrote:
> On Fri 03-02-17 20:32:22, Mel Gorman wrote:
> > Hillf Danton pointed out that since commit 1d82de618dd ("mm, vmscan:
> > make kswapd reclaim in terms of nodes") that PGDAT_WRITEBACK is no longer
> > cleared. It was not noticed as triggering it requires pages under writeback
> > to cycle twice through the LRU and before kswapd gets stalled. Historically,
> > such issues tended to occur on small machines writing heavily to slow
> > storage such as a USB stick. Once kswapd stalls, direct reclaim stalls may
> > be higher but due to the fact that memory pressure is requires, it would not
> > be very noticable. Michal Hocko suggested removing the flag entirely but
> > the conservative fix is to restore the intended PGDAT_WRITEBACK behaviour
> > and clear the flag when a suitable zone is balanced.
> >
> > Signed-off-by: Mel Gorman <mgorman@xxxxxxx>
>
> I agree this is a more conservative approach but I think removing
> PGDAT_WRITEBACK should simplify things a bit.
>
> Acked-by: Michal Hocko <mhocko@xxxxxxxx>
Ohh, an please add
Fixes: 1d82de618ddd ("mm, vmscan: make kswapd reclaim in terms of nodes")
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
