public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Woestenberg <leon.woestenberg@gmail.com>
To: Cliff Brake <cliff.brake@gmail.com>
Cc: rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: rt application question with rs232 communication
Date: Sun, 15 Mar 2009 03:07:13 +0100	[thread overview]
Message-ID: <c384c5ea0903141907o79ccd790h7b48605feaeba107@mail.gmail.com> (raw)
In-Reply-To: <f96d234e0903100544p5bc17143l8916aefd49d78562@mail.gmail.com>

Hello Cliff,

On Tue, Mar 10, 2009 at 1:44 PM, Cliff Brake <cliff.brake@gmail.com> wrote:
> Clarification, I don't have the RT patch applied, just CONFIG_PREEMPT
> from Linus's kernel.  Reviewing my notes from several years ago, I ran
> into a similar issue and the RT patch fixed it, so now to figure out
> the best way to get a recent RT patched ARM kernel ...
>
>> timing.  However, it seems that the system has trouble receiving the
>> response in a timely fashion.  I often observe that it takes at least
>> 10ms for the application to receive the response data after the data
>> has appeared on the rs232 bus.  Is the RT patch something that would

We are running a real-time RS-485 protocol where the time window is 1
ms and only under heavy load we got deadline misses > 1 ms.
Unfortunately I didn't measure the max latency then, but 10 ms sounds
like excessive latency to me.

Under 2.6.24.7-rt24 (or whatever -rtxy in that series) we have never
missed the 1 ms deadline.

That's on XScale IXP4xx @533 MHz,

Regards,
-- 
Leon
--
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

  reply	other threads:[~2009-03-15  2:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-09 21:34 rt application question with rs232 communication Cliff Brake
2009-03-10 12:44 ` Cliff Brake
2009-03-15  2:07   ` Leon Woestenberg [this message]
2009-03-16 20:05     ` Cliff Brake

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=c384c5ea0903141907o79ccd790h7b48605feaeba107@mail.gmail.com \
    --to=leon.woestenberg@gmail.com \
    --cc=cliff.brake@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    /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