From: "K.R. Foley" <kr@cybsft.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rt1
Date: Tue, 21 Mar 2006 20:26:56 -0600 [thread overview]
Message-ID: <4420B5F0.6000201@cybsft.com> (raw)
In-Reply-To: <20060321211653.GA3090@elte.hu>
Ingo Molnar wrote:
> * K.R. Foley <kr@cybsft.com> wrote:
>
>> I haven't had a chance to look into it yet but this combination brings
>> with it a significant latency regression, at least as measured by the
>> rtc histogram stuff.
>
> can you also measure it via rtc_wakeup, a'ka:
>
> chrt -f -p 98 `pidof 'IRQ 8'`
> ./rtc_wakeup -f 8192 -t 100000
>
> ? I have just tried it, and -rt4 looks pretty good on the latency front
> (with all debugging disabled).
>
> Ingo
>
Sorry I have been onsite and completely buried today. Am running an
initial test on both UP and SMP now with 2.6.16-rt1. UP doesn't look bad
at all. SMP on the other hand doesn't look so good. I will give -rt4 a
spin when these are done.
--
kr
next prev parent reply other threads:[~2006-03-22 2:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 8:51 2.6.16-rt1 Ingo Molnar
2006-03-21 4:24 ` 2.6.16-rt1 K.R. Foley
2006-03-21 21:16 ` 2.6.16-rt1 Ingo Molnar
2006-03-22 2:26 ` K.R. Foley [this message]
2006-03-22 6:29 ` 2.6.16-rt1 Ingo Molnar
2006-03-22 14:18 ` 2.6.16-rt1 K.R. Foley
2006-03-22 16:10 ` 2.6.16-rt1 K.R. Foley
2006-03-22 17:31 ` 2.6.16-rt1 Daniel Walker
2006-03-22 20:51 ` 2.6.16-rt1 K.R. Foley
2006-03-23 3:13 ` 2.6.16-rt1 Steven Rostedt
2006-03-21 13:30 ` 2.6.16-rt1 Serge Noiraud
2006-03-21 13:59 ` 2.6.16-rt1 Jan Altenberg
2006-03-21 17:01 ` 2.6.16-rt1 Ingo Molnar
2006-03-21 18:36 ` 2.6.16-rt1 Michal Piotrowski
2006-03-21 20:24 ` 2.6.16-rt1 Ingo Molnar
2006-03-21 23:22 ` 2.6.16-rt1 Michal Piotrowski
-- strict thread matches above, loose matches on Subject: below --
2006-03-22 9:59 2.6.16-rt1 Sébastien Dugué
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=4420B5F0.6000201@cybsft.com \
--to=kr@cybsft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.