linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ying Han <yinghan@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@suse.cz>,
	Johannes Weiner <hannes@cmpxchg.org>, Mel Gorman <mel@csn.ul.ie>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Rik van Riel <riel@redhat.com>, Hillf Danton <dhillf@gmail.com>,
	Hugh Dickins <hughd@google.com>,
	Dan Magenheimer <dan.magenheimer@oracle.com>,
	linux-mm@kvack.org
Subject: Re: [PATCH] mm: fix up the vmscan stat in vmstat
Date: Thu, 12 Apr 2012 17:52:35 -0700	[thread overview]
Message-ID: <CALWz4iz8eWQod4C1dMiMZY-VFi73D_YCLpaFDnjzG7=EyFE-9Q@mail.gmail.com> (raw)
In-Reply-To: <20120412153603.fe320f54.akpm@linux-foundation.org>

On Thu, Apr 12, 2012 at 3:36 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Thu, 12 Apr 2012 11:03:02 -0700
> Ying Han <yinghan@google.com> wrote:
>
>> It is always confusing on stat "pgsteal" where it counts both direct
>> reclaim as well as background reclaim. However, we have "kswapd_steal"
>> which also counts background reclaim value.
>>
>> This patch fixes it and also makes it match the existng "pgscan_" stats.
>>
>> Test:
>> pgsteal_kswapd_dma32 447623
>> pgsteal_kswapd_normal 42272677
>> pgsteal_kswapd_movable 0
>> pgsteal_direct_dma32 2801
>> pgsteal_direct_normal 44353270
>> pgsteal_direct_movable 0
>>
>> Signed-off-by: Ying Han <yinghan@google.com>
>> ---
>>  include/linux/vm_event_item.h |    5 +++--
>>  mm/vmscan.c                   |   11 ++++++++---
>>  mm/vmstat.c                   |    4 ++--
>
> I was going to have a big whine about the failure to update the
> /proc/vmstat documentation.  But we don't have any /proc/vmstat
> documentation.  That was a sneaky labor-saving device.

yeah, there were couple of times that I was looking for the
documentation for vmstat but failed. It turns out that I just need to
quickly look at the source code and find out what each field means.

maybe that gives us a hint only kernel developers cares about them :)

--Ying

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2012-04-13  0:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12 18:03 Ying Han
2012-04-12 18:08 ` Rik van Riel
2012-04-12 18:52 ` Christoph Lameter
2012-04-12 19:05 ` Johannes Weiner
2012-04-12 19:24   ` Ying Han
2012-04-12 19:32     ` Johannes Weiner
2012-04-12 22:36 ` Andrew Morton
2012-04-13  0:52   ` Ying Han [this message]
2012-04-13 14:26   ` Rik van Riel
2012-04-13  0:45 ` Minchan Kim
2012-04-13  1:04 ` KAMEZAWA Hiroyuki
2012-04-13 22:25 Ying Han
2012-04-13 22:26 ` Ying Han

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='CALWz4iz8eWQod4C1dMiMZY-VFi73D_YCLpaFDnjzG7=EyFE-9Q@mail.gmail.com' \
    --to=yinghan@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.magenheimer@oracle.com \
    --cc=dhillf@gmail.com \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=mhocko@suse.cz \
    --cc=riel@redhat.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