From: Roman Gushchin <guro@fb.com>
To: Hugh Dickins <hughd@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>, <linux-mm@kvack.org>,
<kernel-team@fb.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] mm: vmstat: fix /proc/sys/vm/stat_refresh generating false warnings
Date: Thu, 25 Feb 2021 10:06:23 -0800 [thread overview]
Message-ID: <YDfnHyzKzZRU53e4@carbon.dhcp.thefacebook.com> (raw)
In-Reply-To: <alpine.LSU.2.11.2102250905350.11720@eggly.anvils>
On Thu, Feb 25, 2021 at 09:21:04AM -0800, Hugh Dickins wrote:
> On Wed, 24 Feb 2021, Roman Gushchin wrote:
> > On Tue, Feb 23, 2021 at 11:24:23PM -0800, Hugh Dickins wrote:
> > > On Thu, 6 Aug 2020, Andrew Morton wrote:
> > > > On Thu, 6 Aug 2020 16:38:04 -0700 Roman Gushchin <guro@fb.com> wrote:
> > >
> > > August, yikes, I thought it was much more recent.
> > >
> > > >
> > > > > it seems that Hugh and me haven't reached a consensus here.
> > > > > Can, you, please, not merge this patch into 5.9, so we would have
> > > > > more time to find a solution, acceptable for all?
> > > >
> > > > No probs. I already had a big red asterisk on it ;)
> > >
> > > I've a suspicion that Andrew might be tiring of his big red asterisk,
> > > and wanting to unload
> > > mm-vmstat-fix-proc-sys-vm-stat_refresh-generating-false-warnings.patch
> > > mm-vmstat-fix-proc-sys-vm-stat_refresh-generating-false-warnings-fix.patch
> > > mm-vmstat-fix-proc-sys-vm-stat_refresh-generating-false-warnings-fix-2.patch
> > > into 5.12.
> > >
> > > I would prefer not, and reiterate my Nack: but no great harm will
> > > befall the cosmos if he overrules that, and it does go through to
> > > 5.12 - I'll just want to revert it again later. And I do think a
> > > more straightforward way of suppressing those warnings would be just
> > > to delete the code that issues them, rather than brushing them under
> > > a carpet of overtuning.
> >
> > I'm actually fine with either option. My only concern is that if somebody
> > will try to use the hugetlb_cma boot option AND /proc/sys/vm/stat_refresh
> > together, they will get a false warning and report them to mm@ or will
> > waste their time trying to debug a non-existing problem. It's not the end
> > of the world.
> > We can also make the warning conditional on CONFIG_DEBUG_VM, for example.
> >
> > Please, let me know what's your preferred way to go forward.
>
> My preferred way forward (for now: since we're all too busy to fix
> the misbehaving stats) is for Andrew to drop your patch, and I'll post
> three patches against current 5.12 in a few hours: one to restore the
> check on the missing NR_VM_NODE_STAT_ITEMS, one to remove the -EINVAL
> (which upsets test scripts at our end), one to suppress the warning on
> nr_zone_write_pending, nr_writeback and nr_free_cma.
I'd totally support it!
Please, cc me and I'll be happy to review/ack your patches.
Thanks!
prev parent reply other threads:[~2021-02-25 18:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 17:39 Roman Gushchin
2020-07-20 8:03 ` Michal Hocko
2020-07-20 20:20 ` Roman Gushchin
2020-07-30 3:45 ` Hugh Dickins
2020-07-30 16:23 ` Roman Gushchin
2020-07-31 4:06 ` Hugh Dickins
2020-08-01 1:18 ` Roman Gushchin
2020-08-01 2:17 ` Hugh Dickins
2020-08-04 0:40 ` Roman Gushchin
2020-08-06 3:01 ` Hugh Dickins
2020-08-06 3:51 ` Roman Gushchin
2020-08-06 16:41 ` Hugh Dickins
2020-08-06 23:38 ` Roman Gushchin
2020-08-07 0:16 ` Hugh Dickins
2020-08-07 1:25 ` Andrew Morton
2021-02-24 7:24 ` Hugh Dickins
2021-02-25 1:53 ` Roman Gushchin
2021-02-25 17:21 ` Hugh Dickins
2021-02-25 18:06 ` Roman Gushchin [this message]
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=YDfnHyzKzZRU53e4@carbon.dhcp.thefacebook.com \
--to=guro@fb.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=vbabka@suse.cz \
/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