All of lore.kernel.org
 help / color / mirror / Atom feed
From: yong w <yongw.pur@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>, jaewon31.kim@samsung.com
Cc: linux-kernel@vger.kernel.org, mhocko@kernel.org,
	stable@vger.kernel.org, wang.yong12@zte.com.cn,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Minchan Kim <minchan@kernel.org>,
	Mel Gorman <mgorman@techsingularity.net>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v2 stable-4.19 1/3] mm/page_alloc: use ac->high_zoneidx for classzone_idx
Date: Sun, 25 Sep 2022 22:32:32 +0800	[thread overview]
Message-ID: <CAOH5QeBiSEe03KNge9voJ-HjKbNLDoeY2PfKC7HE7F6z-92d7A@mail.gmail.com> (raw)
In-Reply-To: <YzA04ZZI/1OH8oRT@kroah.com>

Greg KH <gregkh@linuxfoundation.org> 于2022年9月25日周日 19:00写道：
>
> On Sun, Sep 25, 2022 at 03:35:27AM -0700, wangyong wrote:
> > From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
> >
> > [ backport of commit 3334a45eb9e2bb040c880ef65e1d72357a0a008b ]
>
> This is from 5.8.  What about the 5.4.y kernel?  Why would someone
> upgrading from 4.19.y to 5.4.y suffer a regression here?
>
I encountered this problem on 4.19, but I haven't encountered it on 5.4.
However, this should be a common problem, so 5.4 may also need to be
merged.

Hello, Joonsoo, what do you think?

> And why wouldn't someone who has this issue just not use 5.10.y instead?
> What prevents someone from moving off of 4.19.y at this point in time?
>
This is a solution, but upgrading the kernel version requires time and overhead,
so use the patch is the most effective way, if there is.

Thanks.
> thanks,
>
> greg k-h

  reply	other threads:[~2022-09-25 14:32 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 [this message]
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=CAOH5QeBiSEe03KNge9voJ-HjKbNLDoeY2PfKC7HE7F6z-92d7A@mail.gmail.com \
    --to=yongw.pur@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=jaewon31.kim@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@kernel.org \
    --cc=minchan@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.