public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Mike Galbraith <bitbucket@online.de>,
	Dave Chiluk <chiluk@canonical.com>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Scheduler accounting inflated for io bound processes.
Date: Wed, 26 Jun 2013 10:13:23 -0600	[thread overview]
Message-ID: <51CB1323.6090305@gmail.com> (raw)
In-Reply-To: <20130626161051.GA8207@gmail.com>

On 6/26/13 10:10 AM, Ingo Molnar wrote:
>> Sampled H/W events have an adaptive period that converges to the desired
>> sampling rate. The first few samples come in 10 usecs are so apart and
>> the time period expands to the desired rate. As I recall that adaptive
>> algorithm starts over every time the event is scheduled in.
>
> Yes, but last I checked it (2 years ago? :-) the auto-freq code was
> converging pretty well to the time clock, with little jitter - in essence
> turning it into a fixed-period, fixed-frequency sampling method. That
> would explain Mike's results.

It does converge quickly and stay there for CPU-based events. My point 
was more along the lines that the code is there. Perhaps a tweak to add 
jitter to the period would address fixed period sampling affects.

David

      reply	other threads:[~2013-06-26 16:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 19:46 Scheduler accounting inflated for io bound processes Dave Chiluk
2013-06-25 16:01 ` Mike Galbraith
2013-06-25 17:48   ` Mike Galbraith
2013-06-26  9:37     ` Ingo Molnar
2013-06-26 10:42       ` Peter Zijlstra
2013-06-26 15:50         ` Ingo Molnar
2013-06-26 16:01           ` Mike Galbraith
2013-06-26 16:04           ` David Ahern
2013-06-26 16:10             ` Ingo Molnar
2013-06-26 16:13               ` David Ahern [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=51CB1323.6090305@gmail.com \
    --to=dsahern@gmail.com \
    --cc=bitbucket@online.de \
    --cc=chiluk@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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