From: Andi Kleen <ak@suse.de>
To: lse-tech@lists.sourceforge.net
Cc: Shailabh Nagar <nagar@watson.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jay Lan <jlan@engr.sgi.com>
Subject: Re: [Lse-tech] [Patch 8/8] /proc export of aggregated block I/O delays
Date: Sat, 22 Apr 2006 09:46:19 +0200 [thread overview]
Message-ID: <200604220946.20010.ak@suse.de> (raw)
In-Reply-To: <44499809.1000301@watson.ibm.com>
On Saturday 22 April 2006 04:42, Shailabh Nagar wrote:
> Changelog
> Fixed comments by akpm
> - use __u64 for delayacct_blkio_ticks() return type
> - redundant check for tsk->delays in __delayacct_blkio_ticks()
I think these basic statistics in /proc are quite useful. Hopefully
top etc. would learn quickly about them too so that normal
people can actually make use of it.
-Andi
next prev parent reply other threads:[~2006-04-22 17:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-22 2:16 [Patch 0/8] per-task delay accounting Shailabh Nagar
2006-04-22 2:23 ` [Patch 1/8] Setup Shailabh Nagar
2006-04-24 2:02 ` Randy.Dunlap
2006-04-24 17:26 ` Shailabh Nagar
2006-04-22 2:29 ` [Patch 2/8] Sync block I/O and swapin delay collection Shailabh Nagar
2006-04-22 2:33 ` [Patch 3/8] cpu delay collection via schedstats Shailabh Nagar
2006-04-22 2:35 ` [Patch 4/8] Utilities for genetlink usage Shailabh Nagar
2006-04-22 2:37 ` [Patch 5/8] taskstats interface Shailabh Nagar
2006-04-27 1:12 ` Jay Lan
2006-04-27 4:00 ` Shailabh Nagar
2006-04-27 6:42 ` [Lse-tech] " Balbir Singh
2006-04-27 17:52 ` Jay Lan
2006-04-27 18:27 ` Balbir Singh
2006-04-27 19:34 ` Jay Lan
2006-04-28 2:59 ` Balbir Singh
2006-04-28 18:20 ` Jay Lan
2006-04-28 18:35 ` Balbir Singh
2006-04-22 2:39 ` [Patch 6/8] delay accounting usage of " Shailabh Nagar
2006-04-22 2:40 ` [Patch 7/8] documentation Shailabh Nagar
2006-04-22 2:42 ` [Patch 8/8] /proc export of aggregated block I/O delays Shailabh Nagar
2006-04-22 7:46 ` Andi Kleen [this message]
2006-04-25 15:07 ` [Patch 0/8] per-task delay accounting Shailabh Nagar
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=200604220946.20010.ak@suse.de \
--to=ak@suse.de \
--cc=jlan@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=nagar@watson.ibm.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
Powered by JetHome