public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tony Luck" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 1/9] ia64: VIRT_CPU_ACCOUNTING (accurate cpu time accounting)
Date: Thu, 01 Nov 2007 20:29:07 +0000	[thread overview]
Message-ID: <12c511ca0711011329k34b538aclbd19c468f102f6d4@mail.gmail.com> (raw)
In-Reply-To: <4714BDC7.1070702@jp.fujitsu.com>

Overall impression: nice!  There have always been some pathalogical
workloads that have confused the scheduler by executing synchronously
with the timer tick ... this should end their tricks.

A couple of comments:

> +         Select this option to enable more accurate task and CPU time
> +         accounting.  This is done by reading a CPU counter on each
> +         kernel entry and exit and on transitions within the kernel
> +         between system, softirq and hardirq state, so there is a
> +         small performance impact.

I haven't tried any macro-level benchmarks, but on a micro-benchmark to
measure system call overhead I see an additional 19-20 cycles in the
cached case. This doesn't look like a "small" performance impact (the
execution time for a syscall in my benchmark is only ~61 cycles).  But
I'd like to see some real benchmarks to see whether the micro-level
problem is measureable at the macro scale.

One warning generated by this patch:
kernel/posix-cpu-timers.c:41: warning: passing arg 1 of
`timespec_to_cputime' discards qualifiers from pointer target type

-Tony

  reply	other threads:[~2007-11-01 20:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 13:33 [PATCH 1/9] ia64: VIRT_CPU_ACCOUNTING (accurate cpu time accounting) Hidetoshi Seto
2007-11-01 20:29 ` Tony Luck [this message]
2007-11-02  3:15 ` Hidetoshi Seto
2007-11-07  6:59 ` Luck, Tony
2007-11-07  9:46 ` Kenji Kaneshige
2007-11-19  4:34 ` Simon Horman
2007-11-19  5:17 ` 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=12c511ca0711011329k34b538aclbd19c468f102f6d4@mail.gmail.com \
    --to=tony.luck@intel.com \
    --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