From: Andrew Morton <akpm@linux-foundation.org>
To: Saurabh Singh Sengar <ssengar@linux.microsoft.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
ssengar@microsoft.com, wei.liu@kernel.org
Subject: Re: [PATCH] mm/vmstat: Defer the refresh_zone_stat_thresholds after all CPUs bringup
Date: Sat, 10 Aug 2024 00:04:04 -0700 [thread overview]
Message-ID: <20240810000404.b08cb06ebbba7e0de9bb8c72@linux-foundation.org> (raw)
In-Reply-To: <20240709045750.GA32083@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
On Mon, 8 Jul 2024 21:57:50 -0700 Saurabh Singh Sengar <ssengar@linux.microsoft.com> wrote:
> > > 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.
> >
> > Did you measure the overall before-and-after times? IOW, how much of
> > that 4.5s do we reclaim?
>
> This entire gain is accounted in over all boot processi time. Most of the Linux
> kernel boot process is sequential and doesn't take advantage of SMP.
Again, if you were able to measure 4.5s without the patch then you are
able to measure how long this delay is with the patch. Please share
that number.
next prev parent reply other threads:[~2024-08-10 7:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 8:48 Saurabh Sengar
2024-07-05 20:59 ` Andrew Morton
2024-07-09 4:57 ` Saurabh Singh Sengar
2024-07-09 21:45 ` Andrew Morton
2024-08-10 7:04 ` Andrew Morton [this message]
2024-08-12 4:37 ` Saurabh Singh Sengar
2024-08-13 23:37 ` Andrew Morton
2024-08-23 15:32 ` Christoph Lameter (Ampere)
2024-08-28 5:37 ` Saurabh Singh Sengar
2024-08-28 15:43 ` Christoph Lameter (Ampere)
2024-08-09 5:20 ` Andrew Morton
2024-08-09 5:49 ` Saurabh Singh Sengar
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=20240810000404.b08cb06ebbba7e0de9bb8c72@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ssengar@linux.microsoft.com \
--cc=ssengar@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