From: tike64 <tike64@yahoo.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: realtime-preempt and arm
Date: Thu, 14 Dec 2006 02:26:56 -0800 (PST) [thread overview]
Message-ID: <297400.29698.qm@web59212.mail.re1.yahoo.com> (raw)
In-Reply-To: <20061214100055.GB19549@elte.hu>
Ingo Molnar <mingo@elte.hu> wrote:
> tike64 <tike64@yahoo.com> wrote:
> > Ok, understood; I tried this:
> >
> > t = raw_timer();
> > ts.tv_nsec = 5000000;
> > ts.tv_sec = 0;
> > nanosleep(&ts, 0);
> > t = raw_timer() - t;
> >
> > It is better but I still see 8ms occasional delays when listing
> > nfs-mounted directories onto FB. And, what is funny, also this
> > version makes the average delay 20ms as if it made the jiffy 20ms.
>
> ARM has no high resolution timers support yet in the -rt tree.
Yes, but is there a reason why the -rt patch seems to make the 10ms
jiffy 20ms and why the jitter is so high. I don't need high resolution
but reasonable, a couple of milliseconds, jitter.
--
tike
____________________________________________________________________________________
Cheap talk?
Check out Yahoo! Messenger's low PC-to-Phone call rates.
http://voice.yahoo.com
next prev parent reply other threads:[~2006-12-14 10:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 8:57 realtime-preempt and arm tike64
2006-11-30 15:56 ` junjiec
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=297400.29698.qm@web59212.mail.re1.yahoo.com \
--to=tike64@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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