From: junjiec@gmail.com
To: tike64@yahoo.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: realtime-preempt and arm
Date: Fri, 01 Dec 2006 00:56:08 +0900 (JST) [thread overview]
Message-ID: <456eff57.0e1fcf5c.617c.44a6@mx.google.com> (raw)
In-Reply-To: <20061129085705.52839.qmail@web57906.mail.re3.yahoo.com>
Hi,
Without the support of High Resolution Timer supported,
the timer resolution wouldn't change.
With high-resolution-timer supported,
our arm926-based board could get resolution like 40~50us.
There are codes you can reference ,may be you should just try to implement it.
JFI, Thanks.
From: tike64 <tike64@yahoo.com>
Subject: realtime-preempt and arm
Date: Wed, 29 Nov 2006 00:57:05 -0800 (PST)
> Hi all,
>
> I'm trying the realtime-preempt patch-2.6.18-rt6 on
> lh7a400 arm system with little success. In a test
> program I try 5 ms timeout with select() but get 20 ms
> avg or 26 ms max. When the framebuffer scrolls, the
> max delay goes up to 59 ms. With a vanilla kernel I
> get 10 ms (because of tick resolution?), 11 ms and 39
> ms.
>
> My question is, is the realtime-preempt patch supposed
> to work on arm architecture and/or without high
> resolution timer (which lh7a40x seems to lack) at all
> or should I just try to be more clever.
>
> Relevant code:
>
> ====
> prio.sched_priority = 99;
> if (sched_setscheduler(0, SCHED_RR, &prio) < 0) ...
> if (mlockall(MCL_CURRENT | MCL_FUTURE) < 0) ...
> while (1) {
> t = raw_timer();
> tv.tv_usec = 5000;
> tv.tv_sec = 0;
> select(0, 0, 0, 0, &tv);
> t = raw_timer() - t;
> if (max_t < t) max_t = t;
> if (min_t > t) min_t = t;
> avg_t += t;
> ++n;
> if (n < 100) continue;
> printf("%i revs; min: %i max: %i avg: %i\n",
> n,
> min_t,
> max_t,
> (avg_t + n / 2) / n);
> ====
>
> Relevant config: PREEMPT_RT, PREEMPT_SOFTIRQS,
> PREEMPT_HARDIRQS
>
> I didnt' enable HIGH_RES_TIMERS because lh7a40x seems
> not to support it.
>
> --
>
> tike
>
>
>
>
> ____________________________________________________________________________________
> Cheap talk?
> Check out Yahoo! Messenger's low PC-to-Phone call rates.
> http://voice.yahoo.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2006-11-30 15:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 8:57 tike64
2006-11-30 15:56 ` junjiec [this message]
2006-12-01 9:07 ` tike64
2006-12-13 18:36 ` Steven Rostedt
2006-12-14 7:21 ` tike64
2006-12-14 10:00 ` Ingo Molnar
2006-12-14 10:26 ` tike64
2006-12-14 12:52 ` Steven Rostedt
2006-12-14 14:23 ` tike64
2006-12-14 15:20 ` Steven Rostedt
2006-12-15 7:15 ` tike64
2006-12-15 9:58 ` Ingo Molnar
2006-12-15 13:00 ` Steven Rostedt
2006-12-16 0:14 Robert Crocombe
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=456eff57.0e1fcf5c.617c.44a6@mx.google.com \
--to=junjiec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tike64@yahoo.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
Powered by JetHome