From: Balbir Singh <balbir@in.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net,
jlan@engr.sgi.com
Subject: [PATCH][delayacct] Add comments on units for the delay fields (was Re: [Patch 2/8] Sync block I/O and swapin delay collection)
Date: Wed, 10 May 2006 15:50:55 +0530 [thread overview]
Message-ID: <20060510102055.GD29432@in.ibm.com> (raw)
In-Reply-To: <20060508141952.2d4b9069.akpm@osdl.org>
On Mon, May 08, 2006 at 02:19:52PM -0700, Andrew Morton wrote:
> Balbir Singh <balbir@in.ibm.com> wrote:
> >
> > @@ -550,6 +550,12 @@ struct task_delay_info {
> > * Atomicity of updates to XXX_delay, XXX_count protected by
> > * single lock above (split into XXX_lock if contention is an issue).
> > */
> > +
> > + struct timespec blkio_start, blkio_end; /* Shared by blkio, swapin */
> > + u64 blkio_delay; /* wait for sync block io completion */
> > + u64 swapin_delay; /* wait for swapin block io completion */
> > + u32 blkio_count;
> > + u32 swapin_count;
>
> These fields are a bit mystifying.
>
> In what units are blkio_delay and swapin_delay?
>
> What is the meaning behind blkio_count and swapin_count?
>
> Better comments needed, please.
Hi, Andrew,
Here is an update, that adds comments to the fields as suggested in the
review comments
Balbir Singh,
Linux Technology Center,
IBM Software Labs
Changelog
1. Add comments to the task_delay_info structure, documenting the units
of delay and document the meaning of the count fields in the structure.
Signed-off-by: Balbir Singh <balbir@in.ibm.com>
---
include/linux/sched.h | 11 +++++++++--
1 files changed, 9 insertions(+), 2 deletions(-)
diff -puN include/linux/sched.h~task-delay-add-comments-on-units include/linux/sched.h
--- linux-2.6.17-rc3/include/linux/sched.h~task-delay-add-comments-on-units 2006-05-10 14:35:46.000000000 +0530
+++ linux-2.6.17-rc3-balbir/include/linux/sched.h 2006-05-10 14:43:39.000000000 +0530
@@ -553,11 +553,18 @@ struct task_delay_info {
* single lock above (split into XXX_lock if contention is an issue).
*/
+ /*
+ * XXX_count is incremented on every XXX operation, the delay
+ * associated with the operation is added to XXX_delay.
+ * XXX_delay contains the accumulated delay time in nanoseconds.
+ */
struct timespec blkio_start, blkio_end; /* Shared by blkio, swapin */
u64 blkio_delay; /* wait for sync block io completion */
u64 swapin_delay; /* wait for swapin block io completion */
- u32 blkio_count;
- u32 swapin_count;
+ u32 blkio_count; /* total count of the number of sync block */
+ /* io operations performed */
+ u32 swapin_count; /* total count of the number of swapin block */
+ /* io operations performed */
};
#endif /* CONFIG_TASK_DELAY_ACCT */
_
prev parent reply other threads:[~2006-05-10 10:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 6:14 [Patch 2/8] Sync block I/O and swapin delay collection Balbir Singh
2006-05-08 21:19 ` Andrew Morton
2006-05-09 3:53 ` Balbir Singh
2006-05-09 4:23 ` Nick Piggin
2006-05-09 5:45 ` Balbir Singh
2006-05-09 5:57 ` Nick Piggin
2006-05-09 8:06 ` Balbir Singh
2006-05-09 8:20 ` Nick Piggin
2006-05-09 17:27 ` Balbir Singh
2006-05-10 0:15 ` Nick Piggin
2006-05-10 10:20 ` Balbir Singh [this message]
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=20060510102055.GD29432@in.ibm.com \
--to=balbir@in.ibm.com \
--cc=akpm@osdl.org \
--cc=jlan@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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