[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <65795E11DBF1E645A09CEC7EAEE94B9CB574E70D@USINDEVS02.corp.hds.com>
Date: Mon, 28 Nov 2011 17:44:08 -0500
From: Satoru Moriya <satoru.moriya@....com>
To: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: "bsingharora@...il.com" <bsingharora@...il.com>,
"mingo@...e.hu" <mingo@...e.hu>,
"peterz@...radead.org" <peterz@...radead.org>,
"nagar@...son.ibm.com" <nagar@...son.ibm.com>,
"kobayashi.kk@...s.nec.co.jp" <kobayashi.kk@...s.nec.co.jp>,
Randy Dunlap <rdunlap@...otime.net>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"dle-develop@...ts.sourceforge.net"
<dle-develop@...ts.sourceforge.net>,
Seiji Aguchi <seiji.aguchi@....com>
Subject: [PATCH 0/4] delayacct: save max CPU/IO/SWAP/RECLAIM delays
In the latency sensitive systems, we usually focus on the worst latency.
And so, it is useful to save max delays into the per-task delay
accounting functionality.
Example output:
(on 100 concurrent dd reading sparse files w/ 1 dd writing a file)
CPU count real total virtual total delay total delay_max delay average
222 45993008 74603882 7637295 3691858 0.034ms
IO count delay total delay max delay average
2 21812073 12728672 10ms
SWAP count delay total delay max delay average
0 0 0 0ms
RECLAIM count delay total delay_max delay average
2 348488 211985 0ms
Any comments are welcome.
Satoru Moriya (4):
sched: add members to struct sched_info to save maximum
delayacct: add members to struct task_delay_info to save max delays
delayacct: update taskstats to save max delays
getdelays: show max CPU/IO/SWAP/RECLAIM delays
Documentation/accounting/getdelays.c | 28 ++++++++++++++----------
Documentation/accounting/taskstats-struct.txt | 9 ++++++++
include/linux/sched.h | 5 ++++
include/linux/taskstats.h | 8 ++++++-
kernel/delayacct.c | 25 +++++++++++++++++----
kernel/sched_stats.h | 5 ++++
6 files changed, 62 insertions(+), 18 deletions(-)
--
1.7.6.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists