From: Balbir Singh <balbir@in.ibm.com>
To: Jay Lan <jlan@engr.sgi.com>
Cc: linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: Re: [Lse-tech] [Patch 6/8] delay accounting usage of taskstats interface
Date: Thu, 4 May 2006 09:53:33 +0530 [thread overview]
Message-ID: <20060504042333.GA6966@in.ibm.com> (raw)
In-Reply-To: <44596362.3080207@engr.sgi.com>
On Wed, May 03, 2006 at 07:13:54PM -0700, Jay Lan wrote:
> Balbir Singh wrote:
> >Changelog
> >
> >Fixes suggested by Jay Lan
> >- check for tidstats before taking the mutex_lock in taskstats_exit_send()
> >- add back version information for struct taskstats
> >
> ><clip>
> >
> > struct taskstats {
> >
> >- /* Version 1 */
> >+ /* Delay accounting fields start
> >+ *
> >+ * All values, until comment "Delay accounting fields end" are
> >+ * available only if delay accounting is enabled, even though the last
> >+ * few fields are not delays
> >+ *
> >+ * xxx_count is the number of delay values recorded
> >+ * xxx_delay_total is the corresponding cumulative delay in nanoseconds
> >+ *
> >+ * xxx_delay_total wraps around to zero on overflow
> >+ * xxx_count incremented regardless of overflow
> >+ */
> >+
> >+ /* Delay waiting for cpu, while runnable
> >+ * count, delay_total NOT updated atomically
> >+ */
> >+ __u64 cpu_count;
> >+ __u64 cpu_delay_total;
> >+
> >+ /* Following four fields atomically updated using task->delays->lock */
> >+
> >+ /* Delay waiting for synchronous block I/O to complete
> >+ * does not account for delays in I/O submission
> >+ */
> >+ __u64 blkio_count;
> >+ __u64 blkio_delay_total;
> >+
> >+ /* Delay waiting for page fault I/O (swap in only) */
> >+ __u64 swapin_count;
> >+ __u64 swapin_delay_total;
> >+
> >+ /* cpu "wall-clock" running time
> >+ * On some architectures, value will adjust for cpu time stolen
> >+ * from the kernel in involuntary waits due to virtualization.
> >+ * Value is cumulative, in nanoseconds, without a corresponding count
> >+ * and wraps around to zero silently on overflow
> >+ */
> >+ __u64 cpu_run_real_total;
> >+
> >+ /* cpu "virtual" running time
> >+ * Uses time intervals seen by the kernel i.e. no adjustment
> >+ * for kernel's involuntary waits due to virtualization.
> >+ * Value is cumulative, in nanoseconds, without a corresponding count
> >+ * and wraps around to zero silently on overflow
> >+ */
> >+ __u64 cpu_run_virtual_total;
> >+ /* Delay accounting fields end */
> >+ /* version 1 ends here */
> >+
> >+ /* version of taskstats */
> >+ __u64 version;
> >
>
> Could you place the common field "version" before any acct subsystem
> specific fields?
>
> As a matter of fact, we do not need
> 'filler_avoids_empty_struct_warnings' in [patch 5/8] taskstats
> interface. Replacing that field with "version" would be great!
Yes, I thought about it and wanted to put it upfront. To maintain compatibility
with the previous post, I decided to add it to the end.
If putting the version right up helps the readability of taskstats.h,
I can make the changes and repost the patches again.
Thanks for your review,
Balbir
next prev parent reply other threads:[~2006-05-04 4:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 6:19 Balbir Singh
2006-05-04 2:13 ` [Lse-tech] " Jay Lan
2006-05-04 4:23 ` Balbir Singh [this message]
2006-05-04 18:44 ` [updated] " Balbir Singh
2006-05-09 11:46 ` Thomas Gleixner
2006-05-09 17:11 ` Balbir Singh
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=20060504042333.GA6966@in.ibm.com \
--to=balbir@in.ibm.com \
--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
Powered by JetHome