linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nikhil Dhama <nikhil.dhama@amd.com>
To: <akpm@linux-foundation.org>
Cc: <bharata@amd.com>, <huang.ying.caritas@gmail.com>,
	<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
	<lkp@intel.com>, <mgorman@techsingularity.net>,
	<nikhil.dhama@amd.com>, <oe-lkp@lists.linux.dev>,
	<raghavendra.kt@amd.com>, <ying.huang@linux.alibaba.com>
Subject: Re: [PATCH v3] mm: pcp: increase pcp->free_count threshold to trigger free_high
Date: Mon, 12 May 2025 12:20:38 +0530	[thread overview]
Message-ID: <20250512065038.22917-1-nikhil.dhama@amd.com> (raw)
In-Reply-To: <20250510213019.0929c25f8c9861d7416df264@linux-foundation.org>

Hi Andrew, 

On 5/11/2025 10:00 AM, Andrew Morton wrote:
> On Mon, 28 Apr 2025 10:30:47 +0530 Nikhil Dhama <nikhil.dhama@amd.com> wrote:
>
>>> Nikhil's attentions are presumably elsewhere.  Could someone (Ying or
>>> Raghavendra?) please send along altered changelog text which I can
>>> paste in there?
>>
>> Please find the updated changelog text as follows:
>
> As far as I can tell, this replacement text is identical to that of the
> orginal patch.
>

As per Ying's suggestion following changes were made to changelog:

In para 1, 

> free_factor by 1 only when we try to reduce the size of pcp list or
> flush for high order, and free_high used to trigger only
> for order > 0 and order < costly_order and pcp->free_factor > 0.

removed "or flush for high order", updating it as 

> free_factor by 1 only when we try to reduce the size of pcp list and
> free_high used to trigger only for order > 0 and order < costly_order
> and pcp->free_factor > 0. 


In para 8, added idea suggested by Ying [1] behind changing the threshold 
from "batch" to  "batch + pcp->high_min / 2". Changed it from, 

> So, in this patch, we increased the pcp->free_count threshold to 
> trigger free_high from "batch" to "batch + pcp->high_min / 2". 

to 

> So, in this patch, we increased the pcp->free_count threshold to
> trigger free_high from "batch" to "batch + pcp->high_min / 2" as
> suggested by Ying [1], In the original pcp->free_factor solution,
> free_high is triggered for contiguous freeing with size ranging from
> "batch" to "pcp->high + batch".  So, the average value is "batch +
> pcp->high / 2".  While in the pcp->free_count solution, free_high will
> be triggered for contiguous freeing with size "batch".  So, to restore
> the original behavior, we can use the threshold "batch + pcp->high_min
> / 2"
[...]
> Link: https://lore.kernel.org/all/875xjmuiup.fsf@DESKTOP-5N7EMDA/ [1]

You seem to already have updated copy in mm tree from the email where I
missed to add linux-mm.

Thanks,
Nikhil


      reply	other threads:[~2025-05-12  6:51 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
2025-04-28  5:00         ` Nikhil Dhama
2025-05-11  4:30           ` Andrew Morton
2025-05-12  6:50             ` Nikhil Dhama [this message]

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=20250512065038.22917-1-nikhil.dhama@amd.com \
    --to=nikhil.dhama@amd.com \
    --cc=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=oe-lkp@lists.linux.dev \
    --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