linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Bai Shuwei" <baishuwei@gmail.com>
To: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: rtlinux rtai interrupt latency
Date: Sun, 21 Oct 2007 10:45:49 +0800	[thread overview]
Message-ID: <f3566d60710201945m3d29830if274e61356c0179@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 274 bytes --]

all, hi
  does anyone knows RTLinux, RTAI interrupt latency and schedule latency on
the PPC440, PPC405?
Thanks!

buroc

-- 

Add: Tianshui South Road 222, Lanzhou, P.R.China
Tel: +86-931-8912025
Zip Code: 730000
URL: oss.lzu.edu.cn
Email: baishuwei@gmail.com, buroc@126.com

[-- Attachment #2: Type: text/html, Size: 490 bytes --]

             reply	other threads:[~2007-10-21  2:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-21  2:45 Bai Shuwei [this message]
2007-10-21  3:24 ` rtlinux rtai interrupt latency Josh Boyer
2007-10-20 20:34   ` Nicholas Mc Guire
2007-10-21 21:25     ` Wolfgang Denk

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=f3566d60710201945m3d29830if274e61356c0179@mail.gmail.com \
    --to=baishuwei@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).