[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOH5QeAUGBshLQdRCWLg9-Q3JvrqROLYW6uWr8a4TBKxwAOPaw@mail.gmail.com>
Date: Wed, 14 Sep 2022 08:46:15 +0800
From: yong w <yongw.pur@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: jaewon31.kim@...sung.com, mhocko@...nel.org,
linux-kernel@...r.kernel.org, stable@...r.kernel.org,
wang.yong12@....com.cn
Subject: Re: [PATCH v4] page_alloc: consider highatomic reserve in watermark fast
Greg KH <gregkh@...uxfoundation.org> 于2022年9月13日周二 21:54写道:
>
> On Tue, Sep 13, 2022 at 09:09:47PM +0800, yong wrote:
> > Hello,
> > This patch is required to be patched in linux-5.4.y and linux-4.19.y.
>
> What is "this patch"? There is no context here :(
>
Sorry, I forgot to quote the original patch. the patch is as follows
f27ce0e page_alloc: consider highatomic reserve in watermark fast
> > In addition to that, the following two patches are somewhat related:
> >
> > 3334a45 mm/page_alloc: use ac->high_zoneidx for classzone_idx
> > 9282012 page_alloc: fix invalid watermark check on a negative value
>
> In what way? What should be done here by us?
>
I think these two patches should also be merged.
The classzone_idx parameter is used in the zone_watermark_fast
functionzone, and 3334a45 use ac->high_zoneidx for classzone_idx.
"9282012 page_alloc: fix invalid watermark check on a negative
value" fix f27ce0e introduced issues
> confused,
>
> greg k-h
Powered by blists - more mailing lists