From: Jaewon Kim <jaewon31.kim@samsung.com>
To: Greg KH <gregkh@linuxfoundation.org>, yong w <yongw.pur@gmail.com>
Cc: Jaewon Kim <jaewon31.kim@samsung.com>,
"mhocko@kernel.org" <mhocko@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"wang.yong12@zte.com.cn" <wang.yong12@zte.com.cn>,
YongTaek Lee <ytk.lee@samsung.com>
Subject: RE: [PATCH v4] page_alloc: consider highatomic reserve in watermark fast
Date: Sun, 18 Sep 2022 10:41:40 +0900 [thread overview]
Message-ID: <1891546521.01663549682346.JavaMail.epsvc@epcpadp4> (raw)
In-Reply-To: <YyREk5hHs2F0eWiE@kroah.com>
>On Wed, Sep 14, 2022 at 08:46:15AM +0800, yong w wrote:
>> Greg KH <gregkh@linuxfoundation.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
>
>Ok, I need an ack by all the developers involved in those commits, as
>well as the subsystem maintainer so that I know it's ok to take them.
>
>Can you provide a series of backported and tested patches so that they
>are easy to review?
>
>thanks,
>
>greg k-h
Hello I didn't know my Act is needed to merge it.
Acked-by: Jaewon Kim <jaewon31.kim@samsung.com>
I don't understand well why the commit f27ce0e has dependency on 3334a45, though.
Thank you
Jaewon Kim
next prev parent reply other threads:[~2022-09-19 1:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 13:09 [PATCH v4] page_alloc: consider highatomic reserve in watermark fast yong
2022-09-13 13:54 ` Greg KH
2022-09-14 0:46 ` yong w
2022-09-16 9:40 ` Greg KH
2022-09-16 17:05 ` [PATCH stable-4.19 0/3] page_alloc: consider highatomic reserve in watermark fast backports to 4.19 wangyong
2022-09-16 17:05 ` [PATCH 1/3] mm/page_alloc: use ac->high_zoneidx for classzone_idx wangyong
2022-09-16 17:09 ` kernel test robot
2022-09-16 17:05 ` [PATCH 2/3] page_alloc: consider highatomic reserve in watermark fast wangyong
2022-09-16 17:05 ` [PATCH 3/3] page_alloc: fix invalid watermark check on a negative value wangyong
2022-09-20 17:41 ` [PATCH stable-4.19 0/3] page_alloc: consider highatomic reserve in watermark fast backports to 4.19 Greg KH
2022-09-25 10:35 ` [PATCH v2 " wangyong
2022-09-25 10:35 ` [PATCH v2 stable-4.19 1/3] mm/page_alloc: use ac->high_zoneidx for classzone_idx wangyong
2022-09-25 10:36 ` kernel test robot
2022-09-25 11:00 ` Greg KH
2022-09-25 14:32 ` yong w
2022-09-26 6:46 ` Greg KH
2022-09-25 10:35 ` [PATCH v2 stable-4.19 2/3] page_alloc: consider highatomic reserve in watermark fast wangyong
2022-09-25 10:35 ` [PATCH v2 stable-4.19 3/3] page_alloc: fix invalid watermark check on a negative value wangyong
2022-10-02 15:37 ` [PATCH v2 stable-4.19 0/3] page_alloc: consider highatomic reserve in watermark fast backports to 4.19 Greg KH
[not found] ` <CAOH5QeB2EqpqQd6fw-P199w8K8-3QNv_t-u_Wn1BLnfaSscmCg@mail.gmail.com>
2022-10-07 16:41 ` Greg KH
2022-10-10 15:47 ` yong w
2022-10-10 15:58 ` Greg KH
2022-09-18 1:41 ` Jaewon Kim [this message]
2022-09-19 13:21 ` [PATCH v4] page_alloc: consider highatomic reserve in watermark fast yong w
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1891546521.01663549682346.JavaMail.epsvc@epcpadp4 \
--to=jaewon31.kim@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wang.yong12@zte.com.cn \
--cc=yongw.pur@gmail.com \
--cc=ytk.lee@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox