From: John Sigler <linux.kernel@free.fr>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: [CONFIG_PREEMPT_RT] High frequency periodic timer
Date: Mon, 02 Jul 2007 15:18:12 +0200 [thread overview]
Message-ID: <4688FB14.90307@free.fr> (raw)
Hello everyone,
I have been experimenting with the CONFIG_PREEMPT_RT patch for a few
months. Specifically kernel 2.6.20.7-rt8.
http://rt.wiki.kernel.org/index.php/Main_Page
I've been running into some unexpected problems, so I wanted to ask
those who have some experience with this patch what they thought.
Here's a brief description of my application:
System A periodically sends timestamped packets. These packets travel
over a network, or through a network emulator, and get randomly dropped
or delayed by a random amount of time. These packets reach system B at
some point. System B uses the timestamp to re-send the packets smoothly,
as if they had been produced on B, with only a constant time-shift.
Basically, B acts as a "dejittering" router.
I have implemented this with high-resolution timers. Every time the
timer fires, I send one packet. In "parallel", I buffer incoming packets
that arrive from system A.
Consider 1316-byte packets and a 80 Mbit/s stream bit rate.
This means the timer period is 1316*8 / 80 = 131.6 µs
I've been wondering whether having such a small period (high frequency)
might be a problem / challenge for the real-time kernel (scheduler, IRQ
handler, other component).
The CPU used is mid-range (i.e. 1.5 GHz Celeron M) single core, and it
easily copes with just the receiving part.
But I have seen some odd behavior (random crashes in my program) that
must mean I have made some incorrect assumptions.
What do you all think?
Regards.
next reply other threads:[~2007-07-02 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 13:18 John Sigler [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-03 13:37 [CONFIG_PREEMPT_RT] High frequency periodic timer John Sigler
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=4688FB14.90307@free.fr \
--to=linux.kernel@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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.