From: Andrew Morton <akpm@linux-foundation.org>
To: "Huang, Ying" <ying.huang@linux.alibaba.com>
Cc: Raghavendra K T <raghavendra.kt@amd.com>,
Nikhil Dhama <nikhil.dhama@amd.com>,
bharata@amd.com, raghavendra.kodsarathimmappa@amd.com,
oe-lkp@lists.linux.dev, lkp@intel.com,
Huang Ying <huang.ying.caritas@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Mel Gorman <mgorman@techsingularity.net>
Subject: Re: [PATCH v3] mm: pcp: increase pcp->free_count threshold to trigger free_high
Date: Fri, 25 Apr 2025 19:11:56 -0700 [thread overview]
Message-ID: <20250425191156.c83d082b1c15e46f77c122b3@linux-foundation.org> (raw)
In-Reply-To: <87mscn5ilt.fsf@DESKTOP-5N7EMDA>
On Fri, 11 Apr 2025 14:15:42 +0800 "Huang, Ying" <ying.huang@linux.alibaba.com> wrote:
> >> in my analysis in
> >> https://lore.kernel.org/all/875xjmuiup.fsf@DESKTOP-5N7EMDA/
> >> If you think my analysis is correct, can you add that in patch
> >> description too? This makes it easier for people to know why the code
> >> looks this way.
> >>
> >
> > Yes. This makes sense. Andrew has already included the patch in mm tree.
> >
> > Nikhil,
> >
> > Could you please help with the updated write up based on Ying's
> > suggestion assuming it works for Andrew?
>
> Thanks!
>
> Just send a updated version, Andrew will update the patch in mm tree
> unless it has been merged by mm-stable.
[ two weeks pass ]
Nikhil's attentions are presumably elsewhere. Could someone (Ying or
Raghavendra?) please send along altered changelog text which I can
paste in there?
next prev parent reply other threads:[~2025-04-26 2:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 10:52 Nikhil Dhama
2025-04-11 2:16 ` Huang, Ying
2025-04-11 6:02 ` Raghavendra K T
2025-04-11 6:15 ` Huang, Ying
2025-04-26 2:11 ` Andrew Morton [this message]
2025-04-28 5:00 ` Nikhil Dhama
2025-05-11 4:30 ` Andrew Morton
2025-05-12 6:50 ` Nikhil Dhama
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=20250425191156.c83d082b1c15e46f77c122b3@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bharata@amd.com \
--cc=huang.ying.caritas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mgorman@techsingularity.net \
--cc=nikhil.dhama@amd.com \
--cc=oe-lkp@lists.linux.dev \
--cc=raghavendra.kodsarathimmappa@amd.com \
--cc=raghavendra.kt@amd.com \
--cc=ying.huang@linux.alibaba.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