From: Hugh Dickins <hughd@google.com>
To: Roman Gushchin <guro@fb.com>
Cc: Hugh Dickins <hughd@google.com>,
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: Fri, 31 Jul 2020 19:17:05 -0700 (PDT) [thread overview]
Message-ID: <alpine.LSU.2.11.2007311915130.9716@eggly.anvils> (raw)
In-Reply-To: <20200801011821.GA859734@carbon.dhcp.thefacebook.com>
On Fri, 31 Jul 2020, Roman Gushchin wrote:
> On Thu, Jul 30, 2020 at 09:06:55PM -0700, Hugh Dickins wrote:
> >
> > Though another alternative did occur to me overnight: we could
> > scrap the logged warning, and show "nr_whatever -53" as output
> > from /proc/sys/vm/stat_refresh: that too would be acceptable
> > to me, and you redirect to /dev/null.
>
> It sounds like a good idea to me. Do you want me to prepare a patch?
Yes, if you like that one best, please do prepare a patch - thanks!
Hugh
next prev parent reply other threads:[~2020-08-01 2:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 17:39 [PATCH v2] mm: vmstat: fix /proc/sys/vm/stat_refresh generating false warnings 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 [this message]
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
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=alpine.LSU.2.11.2007311915130.9716@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--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