From: Ove Karlsen <ove.karlsen@paradoxuncreated.com>
To: tglx@linutronix.de, linux-rt-users@vger.kernel.org
Subject: Re: [ANNOUNCE] 3.6.2-rt4
Date: Mon, 29 Oct 2012 21:39:49 +0100 [thread overview]
Message-ID: <508EE995.3030109@paradoxuncreated.com> (raw)
Hiya, I am switching email-client currently, so excuse a bit of chaos.
I am reading
https://rt.wiki.kernel.org/index.php/Frequently_Asked_Questions#What_sort_of_real-time_performance_should_I_expect.3F
I think it sounds really interesting that you have 10-30uS latencies
back in 2007. The concept sounds thorough and tried then. So I shouldn`t
expect any big SMI messing things up, on my core2duo right?
I think I really wanna get this to work. No solutions? :)
I am reading more here:
https://rt.wiki.kernel.org/index.php/CONFIG_PREEMPT_RT_Patch
"Works ok, but frequency scaling has to be turned off for decent
results. A task run at 1 kHz repetition rate with low load was found to
be t-distributed with 4 degrees of freedom, with 1% value 0.9842 ms, 99%
value 1.0103 ms (ideal realtime performance would get exactly 1 ms for
both values), with the frequency governor set to "performance"."
Quite low. So he has got it running with low jitter, on a core 2 quad.
SMI sounds not much of a problem then. I want this guys. Altough as said
I am buying a computer, particulary for low-jitter, we can always try
and make this work on my older box in the mean time.
Remember the prob is with threadirqs on mainline aswell. Could it be
some clockproblem? A task for the thirsty bughunter, and patch-glory to
mainline.
--
Fred være med deg / Peace Be with You,
Ove Karlsen
http://www.paradoxuncreated.com
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2012-10-29 20:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 20:39 Ove Karlsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-26 21:45 [ANNOUNCE] 3.6.2-rt4 Uwaysi Bin Kareem
2012-10-26 21:54 ` Paul Gortmaker
2012-10-26 22:24 ` Uwaysi Bin Kareem
2012-10-27 0:17 ` Sven-Thorsten Dietrich
2012-10-27 9:41 ` Uwaysi Bin Kareem
2012-10-27 9:50 ` Uwaysi Bin Kareem
2012-10-20 19:40 Thomas Gleixner
2012-10-22 21:54 ` Paul Gortmaker
[not found] ` <op.wmk8f6m96426ze@localhost.localdomain>
[not found] ` <alpine.LFD.2.02.1210222029480.2756@ionos>
2012-10-22 21:05 ` Uwaysi Bin Kareem
2012-10-23 6:52 ` Thomas Gleixner
2012-10-23 22:53 ` Uwaysi Bin Kareem
2012-10-24 5:01 ` Sven-Thorsten Dietrich
2012-10-24 8:16 ` Uwaysi Bin Kareem
2012-10-24 9:59 ` Thomas Gleixner
2012-10-24 10:48 ` Uwaysi Bin Kareem
2012-10-24 14:27 ` Thomas Gleixner
2012-10-24 17:06 ` Uwaysi Bin Kareem
2012-10-24 18:38 ` Thomas Gleixner
2012-10-24 18:47 ` Uwaysi Bin Kareem
2012-10-24 19:24 ` Thomas Gleixner
2012-10-24 19:32 ` Uwaysi Bin Kareem
2012-10-24 19:49 ` Thomas Gleixner
2012-10-24 19:57 ` Uwaysi Bin Kareem
2012-10-25 21:21 ` Thomas Gleixner
2012-10-26 14:24 ` Paul Gortmaker
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=508EE995.3030109@paradoxuncreated.com \
--to=ove.karlsen@paradoxuncreated.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).