From: Peter Zijlstra <peterz@infradead.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: 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 12:42:43 +0200 [thread overview]
Message-ID: <20130626104243.GE28407@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20130626093713.GA27385@gmail.com>
On Wed, Jun 26, 2013 at 11:37:13AM +0200, Ingo Molnar wrote:
> Would be very nice to randomize the sampling rate, by randomizing the
> intervals within a 1% range or so - perf tooling will probably recognize
> the different weights.
You're suggesting adding noise to the regular kernel tick?
next prev parent reply other threads:[~2013-06-26 15:29 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 [this message]
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
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=20130626104243.GE28407@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bitbucket@online.de \
--cc=chiluk@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
/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