From: "Srivatsa S. Bhat" <srivatsa@csail.mit.edu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Saurabh Singh Sengar <ssengar@microsoft.com>,
Saurabh Sengar <ssengar@linux.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>,
"cl@linux.com" <cl@linux.com>
Subject: Re: [PATCH v2] mm/vmstat: Defer the refresh_zone_stat_thresholds after all CPUs bringup
Date: Fri, 20 Sep 2024 09:25:48 +0000 [thread overview]
Message-ID: <Zu0/nKB5oRF8Yvdk@csail.mit.edu> (raw)
In-Reply-To: <20240920011618.bb2d2a247ae59810aee6c39c@linux-foundation.org>
On Fri, Sep 20, 2024 at 01:16:18AM -0700, Andrew Morton wrote:
> On Thu, 19 Sep 2024 19:52:45 +0000 Saurabh Singh Sengar <ssengar@microsoft.com> wrote:
>
> > > > >
> > >
> > > Adding cl@linux.com instead of clameter@sgi.com for Christoph Lameter
> > >
> > > - Saurabh
> >
> > Hi Andrew,
> >
> > Can we get this merge in for next kernel release.
> > Please let me know if there is any concern with this patch.
> >
>
> Anshuman's review comment remains unaddressed:
> https://lkml.kernel.org/r/b1dc2aa1-cd38-4f1f-89e9-6d009a619541@arm.com
>
> Also, Christoph's observations from the v1 patch review haven't really
> been addressed.
>
> So it sounds to me that an alternative implementation should be
> investigated?
I believe Saurabh had a follow-up discussion in person with Christoph
regarding this patch, following our talk on this topic at LPC:
https://lpc.events/event/18/contributions/1817/
@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?
Thanks a lot!
Regards,
Srivatsa
Microsoft Linux Systems Group
next prev parent reply other threads:[~2024-09-20 9:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 6:13 [PATCH v2] mm/vmstat: Defer the refresh_zone_stat_thresholds after all CPUs bringup 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 [this message]
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=Zu0/nKB5oRF8Yvdk@csail.mit.edu \
--to=srivatsa@csail.mit.edu \
--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=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