From: Ingo Molnar <mingo@redhat.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Matt Mackall <mpm@selenic.com>,
jackit-devel <jackit-devel@lists.sourceforge.net>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel <linux-kernel@vger.kernel.org>,
Peter Williams <pwil3058@bigpond.net.au>
Subject: Re: [Jackit-devel] Re: Statistical methods for latency profiling
Date: Sun, 1 Aug 2004 07:21:17 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0408010717290.23711@devserv.devel.redhat.com> (raw)
In-Reply-To: <1091339954.20819.243.camel@mindpipe>
On Sun, 1 Aug 2004, Lee Revell wrote:
> So stressing the filesystem moves the center to the right a bit, from
> 6-7 to 9-10, and *drastically* lengthens the 'tail'.
basically each codepath has a typical latency distribution, and when a
workload uses multiple codepaths then the latencies get intermixed almost
linearly.
> These numbers suggest to me that a lot of the latencies from 47 usecs
> and up are caused by one code path, because they are so uniformly
> distributed over the upper part of the histogram. The prime suspect of
> course being the ide io completions. I tested this theory by lowering
> max_sectors_kb from 64 to 32:
> These numbers all point to the ide sg completion code as the only thing
> on the system generating latencies over ~42 usecs.
yep, that's a fair assumption. Once the IO-APIC irq-redirection problems
are solved i'll try to further thread the IDE completion IRQ to remove
that ~100 usecs latency.
Ingo
next prev parent reply other threads:[~2004-08-01 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-31 5:22 Lee Revell
2004-08-01 2:55 ` Matt Mackall
2004-08-01 3:24 ` [Jackit-devel] " Lee Revell
2004-08-01 5:59 ` Lee Revell
2004-08-01 11:21 ` Ingo Molnar [this message]
2004-08-01 11:53 ` Lee Revell
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=Pine.LNX.4.58.0408010717290.23711@devserv.devel.redhat.com \
--to=mingo@redhat.com \
--cc=jackit-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mpm@selenic.com \
--cc=pwil3058@bigpond.net.au \
--cc=rlrevell@joe-job.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
all inboxes | Powered by JetHome®