[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zu0/nKB5oRF8Yvdk@csail.mit.edu>
Date: Fri, 20 Sep 2024 09:25:48 +0000
From: "Srivatsa S. Bhat" <srivatsa@...il.mit.edu>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Saurabh Singh Sengar <ssengar@...rosoft.com>,
Saurabh Sengar <ssengar@...ux.microsoft.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"wei.liu@...nel.org" <wei.liu@...nel.org>,
"mgorman@...hsingularity.net" <mgorman@...hsingularity.net>,
"cl@...ux.com" <cl@...ux.com>
Subject: Re: [PATCH v2] mm/vmstat: Defer the refresh_zone_stat_thresholds
after all CPUs bringup
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@...rosoft.com> wrote:
>
> > > > >
> > >
> > > Adding cl@...ux.com instead of clameter@....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
Powered by blists - more mailing lists