From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"hugh.dickins@tiscali.co.uk" <hugh.dickins@tiscali.co.uk>,
cl@linux-foundation.org, akpm@linux-foundation.org
Subject: Re: [PATCH] show per-process swap usage via procfs
Date: Thu, 5 Nov 2009 23:41:50 +0900 [thread overview]
Message-ID: <2f11576a0911050641j8799c5kbd390116edcc566d@mail.gmail.com> (raw)
In-Reply-To: <20091104152426.eacc894f.kamezawa.hiroyu@jp.fujitsu.com>
2009/11/4 KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>:
>
> Passed several tests and one bug was fixed since RFC version.
> This patch is against mmotm.
> =
> From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
>
> Now, anon_rss and file_rss is counted as RSS and exported via /proc.
> RSS usage is important information but one more information which
> is often asked by users is "usage of swap".(user support team said.)
>
> This patch counts swap entry usage per process and show it via
> /proc/<pid>/status. I think status file is robust against new entry.
> Then, it is the first candidate..
>
> After this, /proc/<pid>/status includes following line
> <snip>
> VmPeak: 315360 kB
> VmSize: 315360 kB
> VmLck: 0 kB
> VmHWM: 180452 kB
> VmRSS: 180452 kB
> VmData: 311624 kB
> VmStk: 84 kB
> VmExe: 4 kB
> VmLib: 1568 kB
> VmPTE: 640 kB
> VmSwap: 131240 kB <=== new information
>
> Note:
> Because this patch catches swap_pte on page table, this will
> not catch shmem's swapout. It's already accounted in per-shmem
> inode and we don't need to do more.
Sidenote: top(1) can show SWAP usage. but it is crazy buggy
implementation. it define
VIRT = SWAP + RES (see man top or actual source code). this patch help
to fix its insane
calculation.
Acked-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-11-05 14:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 6:24 KAMEZAWA Hiroyuki
2009-11-04 19:15 ` Christoph Lameter
2009-11-04 23:25 ` KOSAKI Motohiro
2009-11-05 2:28 ` KAMEZAWA Hiroyuki
2009-11-05 15:04 ` Christoph Lameter
2009-11-08 17:04 ` Pavel Machek
2009-11-05 0:06 ` KAMEZAWA Hiroyuki
2009-11-05 5:16 ` [RFC][PATCH] lib: generic percpu counter array KAMEZAWA Hiroyuki
2009-11-05 15:15 ` Christoph Lameter
2009-11-06 0:49 ` KAMEZAWA Hiroyuki
2009-11-05 15:20 ` Christoph Lameter
2009-11-06 0:56 ` KAMEZAWA Hiroyuki
2009-11-05 14:41 ` KOSAKI Motohiro [this message]
2009-11-05 15:11 ` [PATCH] show per-process swap usage via procfs Minchan Kim
2009-11-05 23:48 ` KAMEZAWA Hiroyuki
2009-11-06 4:40 ` [PATCH] show per-process swap usage via procfs v2 KAMEZAWA Hiroyuki
2009-11-06 15:19 ` Minchan Kim
2009-11-11 2:25 ` [PATCH] show per-process swap usage via procfs v3 KAMEZAWA Hiroyuki
2009-11-12 15:20 ` Christoph Lameter
2009-11-13 1:51 ` KAMEZAWA Hiroyuki
2009-11-13 2:35 ` KAMEZAWA Hiroyuki
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=2f11576a0911050641j8799c5kbd390116edcc566d@mail.gmail.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=hugh.dickins@tiscali.co.uk \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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