From: Peter Chubb <peterc@gelato.unsw.edu.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 9/9] ia64: VIRT_CPU_ACCOUNTING (accurate cpu time accounting)
Date: Wed, 17 Oct 2007 03:35:05 +0000 [thread overview]
Message-ID: <87ejfuxvkm.wl%peter@chubb.wattle.id.au> (raw)
In-Reply-To: <4714BF9C.6090308@jp.fujitsu.com>
>>>>> "Hidetoshi" = Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com> writes:
>> [9/9] ia64_acct_get_vtime.patch
Hidetoshi> Now all check points are ready.
Hidetoshi> We already cumulate cycles for stime/utime on kernel
Hidetoshi> entrance/exit, so what we need to do is reflecting them
Hidetoshi> into stime/utime of the thread, after translating cycles to
Hidetoshi> nsec.
This patchset duplicates some of the Microstate Accounting patchset
(which attempts to keep track of time spent in various states for each
thread). As such I've had some experience trying to do this stuff.
Things to watch are:
-- With Montvale and later, the processor clock speed can be
varied via ACPI. Does ITC rate change? In additon, KVM can
virtualise ITC (although it doesn't at present)
-- ITC is not synchronised across multiple processors. I don't think
this'll be an issue for you as you're only measuring time on-cpu,
and migration necessarily goes via a run queue.
-- Adding ACCOUNT_SYS_ENTER adds around 40 cycles to the system
call path. If you wanted, you could move reading ITC earlier (it
takes up to 36 cycles), and overlap with other work.
Peter C
--
Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au
http://www.ertos.nicta.com.au ERTOS within National ICT Australia
next prev parent reply other threads:[~2007-10-17 3:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 13:41 [PATCH 9/9] ia64: VIRT_CPU_ACCOUNTING (accurate cpu time accounting) Hidetoshi Seto
2007-10-17 3:35 ` Peter Chubb [this message]
2007-10-17 4:36 ` peterc
2007-10-17 8:16 ` Hidetoshi Seto
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=87ejfuxvkm.wl%peter@chubb.wattle.id.au \
--to=peterc@gelato.unsw.edu.au \
--cc=linux-ia64@vger.kernel.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