From: Nikhil Dhama <nikhil.dhama@amd.com>
To: <akpm@linux-foundation.org>
Cc: <raghavendra.kodsarathimmappa@amd.com>, <bharata@amd.com>,
<huang.ying.caritas@gmail.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <subramaniam.kv@amd.com>,
<santosh.shukla@amd.com>, <shivankg@amd.com>,
Nikhil Dhama <nikhil.dhama@amd.com>
Subject: Re: [FIX PATCH] mm: pcp: fix pcp->free_count reduction on page allocation
Date: Thu, 9 Jan 2025 17:12:29 +0530 [thread overview]
Message-ID: <20250109114230.24203-1-nikhil.dhama@amd.com> (raw)
In-Reply-To: <20250107210506.3336da0da4332002847c89a3@linux-foundation.org>
> The present division by two appears to be somewhat randomly chosen.
> And as far as I can tell, this patch proposes replacing that with
> another somewhat random adjustment.
>
> What's the actual design here? What are we attempting to do and why,
> and why is the proposed design superior to the present one?
We are further analyzing both the designs and their impact on pcp list.
> Nice, but might other workloads on other machines get slower?
We are studying the impact of this on other network workloads like netperf,
and will post those results soon.
next prev parent reply other threads:[~2025-01-09 11:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 9:17 Nikhil Dhama
2025-01-08 5:05 ` Andrew Morton
2025-01-09 11:42 ` Nikhil Dhama [this message]
2025-01-15 11:06 ` Huang, Ying
2025-01-15 11:19 ` [FIX PATCH] mm: pcp: fix pcp->free_count reduction on page allocation, Huang, Ying
2025-01-29 4:31 ` Andrew Morton
2025-02-12 5:04 ` [FIX PATCH] mm: pcp: fix pcp->free_count reduction on page allocation Nikhil Dhama
2025-02-12 8:40 ` Huang, Ying
2025-02-12 10:06 ` Nikhil Dhama
2025-03-19 8:14 ` [PATCH -V2] mm: pcp: scale batch to reduce number of high order pcp flushes on deallocation Nikhil Dhama
2025-03-25 8:00 ` Raghavendra K T
2025-03-25 17:23 ` 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=20250109114230.24203-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=raghavendra.kodsarathimmappa@amd.com \
--cc=santosh.shukla@amd.com \
--cc=shivankg@amd.com \
--cc=subramaniam.kv@amd.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