From: Saurabh Singh Sengar <ssengar@linux.microsoft.com>
To: "Christoph Lameter (Ampere)" <cl@gentwo.org>
Cc: "Srivatsa S. Bhat" <srivatsa@csail.mit.edu>,
Andrew Morton <akpm@linux-foundation.org>,
Saurabh Singh Sengar <ssengar@microsoft.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"wei.liu@kernel.org" <wei.liu@kernel.org>,
"mgorman@techsingularity.net" <mgorman@techsingularity.net>
Subject: Re: [PATCH v2] mm/vmstat: Defer the refresh_zone_stat_thresholds after all CPUs bringup
Date: Tue, 24 Sep 2024 00:39:47 -0700 [thread overview]
Message-ID: <20240924073947.GA22582@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <529015dc-403c-7cc0-5b66-95739e1c78d2@gentwo.org>
On Mon, Sep 23, 2024 at 01:17:16PM -0700, Christoph Lameter (Ampere) wrote:
> On Fri, 20 Sep 2024, Srivatsa S. Bhat wrote:
>
> > @Christoph, would you mind giving your Ack if this patch v2 looks good
> > to you, or kindly point out if there are any lingering concerns?
>
> V2 looks good to me (unitialized pcp values result in slow operation but
> no negative other effects) and the late_initcall() is always executed.
>
> Acked-by: Christoph Lameter <cl@linux.com>
Thank you, Christoph. I truly appreciate your review and insights on this matter.
Looking forward to collobrate more on similar space.
- Saurabh
next prev parent reply other threads:[~2024-09-24 7:39 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
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 [this message]
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=20240924073947.GA22582@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
--to=ssengar@linux.microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=srivatsa@csail.mit.edu \
--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