From: Saurabh Singh Sengar <ssengar@microsoft.com>
To: Saurabh Singh Sengar <ssengar@microsoft.com>,
Saurabh Sengar <ssengar@linux.microsoft.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "wei.liu@kernel.org" <wei.liu@kernel.org>,
"srivatsa@csail.mit.edu" <srivatsa@csail.mit.edu>,
"mgorman@techsingularity.net" <mgorman@techsingularity.net>,
"cl@linux.com" <cl@linux.com>
Subject: RE: [PATCH v2] mm/vmstat: Defer the refresh_zone_stat_thresholds after all CPUs bringup
Date: Fri, 23 Aug 2024 09:32:26 +0000 [thread overview]
Message-ID: <TYZP153MB0796B44322EAE4C712883201BE882@TYZP153MB0796.APCP153.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <TYZP153MB07963DDE4B7E01C575B143E2BE882@TYZP153MB0796.APCP153.PROD.OUTLOOK.COM>
> -----Original Message-----
> From: Saurabh Singh Sengar <ssengar@microsoft.com>
> Sent: 23 August 2024 15:00
> To: Saurabh Sengar <ssengar@linux.microsoft.com>; akpm@linux-
> foundation.org; linux-mm@kvack.org; linux-kernel@vger.kernel.org
> Cc: wei.liu@kernel.org; srivatsa@csail.mit.edu; clameter@sgi.com;
> mgorman@techsingularity.net
> Subject: [EXTERNAL] RE: [PATCH v2] mm/vmstat: Defer the
> refresh_zone_stat_thresholds after all CPUs bringup
>
>
>
> > -----Original Message-----
> > From: Saurabh Sengar <ssengar@linux.microsoft.com>
> > Sent: 12 August 2024 11:44
> > To: akpm@linux-foundation.org; linux-mm@kvack.org; linux-
> > kernel@vger.kernel.org
> > Cc: Saurabh Singh Sengar <ssengar@microsoft.com>; wei.liu@kernel.org;
> > srivatsa@csail.mit.edu
> > Subject: [PATCH v2] mm/vmstat: Defer the refresh_zone_stat_thresholds
> > after all CPUs bringup
> >
> > refresh_zone_stat_thresholds function has two loops which is expensive
> > for higher number of CPUs and NUMA nodes.
> >
> > Below is the rough estimation of total iterations done by these loops
> > based on number of NUMA and CPUs.
> >
> > Total number of iterations: nCPU * 2 * Numa * mCPU
> > Where:
> > nCPU = total number of CPUs
> > Numa = total number of NUMA nodes
> > mCPU = mean value of total CPUs (e.g., 512 for 1024 total CPUs)
> >
> > For the system under test with 16 NUMA nodes and 1024 CPUs, this
> > results in a substantial increase in the number of loop iterations
> > during boot-up when NUMA is enabled:
> >
> > No NUMA = 1024*2*1*512 = 1,048,576 : Here
> refresh_zone_stat_thresholds
> > takes around 224 ms total for all the CPUs in the system under test.
> > 16 NUMA = 1024*2*16*512 = 16,777,216 : Here
> > refresh_zone_stat_thresholds takes around 4.5 seconds total for all
> > the CPUs in the system under test.
> >
> > Calling this for each CPU is expensive when there are large number of
> > CPUs along with multiple NUMAs. Fix this by deferring
> > refresh_zone_stat_thresholds to be called later at once when all the
> > secondary CPUs are up. Also, register the DYN hooks to keep the
> > existing hotplug functionality intact.
> >
> > Signed-off-by: Saurabh Sengar <ssengar@linux.microsoft.com>
>
> CC: Mel Gorman and Christoph Lameter
Adding cl@linux.com instead of clameter@sgi.com for Christoph Lameter
- Saurabh
next prev parent reply other threads:[~2024-08-23 9:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 6:13 Saurabh Sengar
2024-08-23 9:30 ` Saurabh Singh Sengar
2024-08-23 9:32 ` Saurabh Singh Sengar [this message]
2024-09-19 19:52 ` Saurabh Singh Sengar
2024-09-20 8:16 ` Andrew Morton
2024-09-20 9:25 ` Srivatsa S. Bhat
2024-09-23 20:17 ` Christoph Lameter (Ampere)
2024-09-24 2:56 ` Srivatsa S. Bhat
2024-09-24 7:40 ` Saurabh Singh Sengar
2024-09-24 7:39 ` Saurabh Singh Sengar
2024-09-20 6:58 ` Anshuman Khandual
2024-09-20 9:14 ` Srivatsa S. Bhat
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=TYZP153MB0796B44322EAE4C712883201BE882@TYZP153MB0796.APCP153.PROD.OUTLOOK.COM \
--to=ssengar@microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=srivatsa@csail.mit.edu \
--cc=ssengar@linux.microsoft.com \
--cc=wei.liu@kernel.org \
/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