[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YD0EOyW3pZXDnuuJ@cmpxchg.org>
Date: Mon, 1 Mar 2021 10:11:55 -0500
From: Johannes Weiner <hannes@...xchg.org>
To: Pintu Kumar <pintu@...eaurora.org>
Cc: linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
linux-mm@...ck.org, linux-fsdevel@...r.kernel.org,
linux-doc@...r.kernel.org, jaewon31.kim@...sung.com,
yuzhao@...gle.com, shakeelb@...gle.com, guro@...com,
mchehab+huawei@...nel.org, xi.fengfei@....com,
lokeshgidra@...gle.com, nigupta@...dia.com, famzheng@...zon.com,
andrew.a.klychkov@...il.com, bigeasy@...utronix.de,
ping.ping@...il.com, vbabka@...e.cz, yzaikin@...gle.com,
keescook@...omium.org, mcgrof@...nel.org, corbet@....net,
pintu.ping@...il.com
Subject: Re: [PATCH] mm: introduce clear all vm events counters
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?
Powered by blists - more mailing lists