From: wangyong <yongw.pur@gmail.com>
To: gregkh@linuxfoundation.org
Cc: jaewon31.kim@samsung.com, linux-kernel@vger.kernel.org,
mhocko@kernel.org, stable@vger.kernel.org,
wang.yong12@zte.com.cn, yongw.pur@gmail.com
Subject: [PATCH v2 stable-4.19 0/3] page_alloc: consider highatomic reserve in watermark fast backports to 4.19
Date: Sun, 25 Sep 2022 03:35:26 -0700 [thread overview]
Message-ID: <20220925103529.13716-1-yongw.pur@gmail.com> (raw)
In-Reply-To: <Yyn7MoSmV43Gxog4@kroah.com>
Here are the corresponding backports to 4.19.
And fix classzone_idx context differences causing patch merge conflicts.
Original commit IDS:
3334a45 mm/page_alloc: use ac->high_zoneidx for classzone_idx
f27ce0e page_alloc: consider highatomic reserve in watermark fast
9282012 page_alloc: fix invalid watermark check on a negative value
Changes from v1:
- Add commit information of the original patches.
Jaewon Kim (2):
page_alloc: consider highatomic reserve in watermark fast
page_alloc: fix invalid watermark check on a negative value
Joonsoo Kim (1):
mm/page_alloc: use ac->high_zoneidx for classzone_idx
mm/internal.h | 2 +-
mm/page_alloc.c | 69 +++++++++++++++++++++++++++++++++------------------------
2 files changed, 41 insertions(+), 30 deletions(-)
--
2.7.4
next prev parent reply other threads:[~2022-09-25 10:36 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 ` wangyong [this message]
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
[not found] ` <CGME20220916094017epcas1p1deed4041f897d2bf0e0486554d79b3af@epcms1p4>
2022-09-18 1:41 ` [PATCH v4] page_alloc: consider highatomic reserve in watermark fast Jaewon Kim
2022-09-19 13:21 ` 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=20220925103529.13716-1-yongw.pur@gmail.com \
--to=yongw.pur@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jaewon31.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wang.yong12@zte.com.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.