Re: [PATCH] mm, page_alloc: reset the zone->watermark_boost early

2020-05-13 Thread Andrew Morton
On Wed, 13 May 2020 15:16:53 +0530 Charan Teja Kalla wrote: > So, yes, this problem is got fixed with the changes made in this patch. OK, thanks. Could you please prepare a v2 with a changelog which includes the additional info in your two replies?

Re: [PATCH] mm, page_alloc: reset the zone->watermark_boost early

2020-05-13 Thread Charan Teja Kalla
On 5/12/2020 7:01 PM, Charan Teja Kalla wrote: > > Thank you Andrew for the reply. > > On 5/12/2020 1:41 AM, Andrew Morton wrote: >> On Mon, 11 May 2020 19:10:08 +0530 Charan Teja Reddy >> wrote: >> >>> Updating the zone watermarks by any means, like extra_free_kbytes, >>> min_free_kbytes, w

Re: [PATCH] mm, page_alloc: reset the zone->watermark_boost early

2020-05-12 Thread Charan Teja Kalla
Thank you Andrew for the reply. On 5/12/2020 1:41 AM, Andrew Morton wrote: > On Mon, 11 May 2020 19:10:08 +0530 Charan Teja Reddy > wrote: > >> Updating the zone watermarks by any means, like extra_free_kbytes, >> min_free_kbytes, water_mark_scale_factor e.t.c, when watermark_boost is >> set

Re: [PATCH] mm, page_alloc: reset the zone->watermark_boost early

2020-05-11 Thread Andrew Morton
On Mon, 11 May 2020 19:10:08 +0530 Charan Teja Reddy wrote: > Updating the zone watermarks by any means, like extra_free_kbytes, > min_free_kbytes, water_mark_scale_factor e.t.c, when watermark_boost is > set will result into the higher low and high watermarks than the user > asks. This can be a

[PATCH] mm, page_alloc: reset the zone->watermark_boost early

2020-05-11 Thread Charan Teja Reddy
Updating the zone watermarks by any means, like extra_free_kbytes, min_free_kbytes, water_mark_scale_factor e.t.c, when watermark_boost is set will result into the higher low and high watermarks than the user asks. This can be avoided by resetting the zone->watermark_boost to zero early. Signed-of