From: Johannes Weiner <hannes@cmpxchg.org>
To: Pintu Kumar <pintu@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org, jaewon31.kim@samsung.com,
yuzhao@google.com, shakeelb@google.com, guro@fb.com,
mchehab+huawei@kernel.org, xi.fengfei@h3c.com,
lokeshgidra@google.com, nigupta@nvidia.com, famzheng@amazon.com,
andrew.a.klychkov@gmail.com, bigeasy@linutronix.de,
ping.ping@gmail.com, vbabka@suse.cz, yzaikin@google.com,
keescook@chromium.org, mcgrof@kernel.org, corbet@lwn.net,
pintu.ping@gmail.com
Subject: Re: [PATCH] mm: introduce clear all vm events counters
Date: Mon, 1 Mar 2021 10:11:55 -0500 [thread overview]
Message-ID: <YD0EOyW3pZXDnuuJ@cmpxchg.org> (raw)
In-Reply-To: <1614595766-7640-1-git-send-email-pintu@codeaurora.org>
On Mon, Mar 01, 2021 at 04:19:26PM +0530, Pintu Kumar wrote:
> At times there is a need to regularly monitor vm counters while we
> reproduce some issue, or it could be as simple as gathering some system
> statistics when we run some scenario and every time we like to start from
> beginning.
> The current steps are:
> Dump /proc/vmstat
> Run some scenario
> Dump /proc/vmstat again
> Generate some data or graph
> reboot and repeat again
You can subtract the first vmstat dump from the second to get the
event delta for the scenario run. That's what I do, and I'd assume
most people are doing. Am I missing something?
next prev parent reply other threads:[~2021-03-01 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 10:49 [PATCH] mm: introduce clear all vm events counters Pintu Kumar
2021-03-01 12:13 ` Matthew Wilcox
2021-03-01 13:55 ` pintu
2021-03-01 15:11 ` Johannes Weiner [this message]
2021-03-02 10:30 ` pintu
2021-03-02 15:56 ` Johannes Weiner
2021-03-03 12:25 ` pintu
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=YD0EOyW3pZXDnuuJ@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=andrew.a.klychkov@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=corbet@lwn.net \
--cc=famzheng@amazon.com \
--cc=guro@fb.com \
--cc=jaewon31.kim@samsung.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lokeshgidra@google.com \
--cc=mcgrof@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=nigupta@nvidia.com \
--cc=ping.ping@gmail.com \
--cc=pintu.ping@gmail.com \
--cc=pintu@codeaurora.org \
--cc=shakeelb@google.com \
--cc=vbabka@suse.cz \
--cc=xi.fengfei@h3c.com \
--cc=yuzhao@google.com \
--cc=yzaikin@google.com \
/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;
as well as URLs for NNTP newsgroup(s).