From: John Schipper <jschipper@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-core] Isolated CPU, SMI problems an thoughts
Date: Thu, 09 Feb 2006 10:49:48 -0700 [thread overview]
Message-ID: <43EB80BC.1060403@domain.hid> (raw)
Hello,
I'm new to this list but have in the past used RTAI in a single
processor off the shelf solution. I'm looking to switch to native
Xenomai api but have a general problem...
The problem is SMI on new systems, and other latency killers that
sometimes are not controllable by software always popping up when trying
to migrate to a newer platform. Can a dual core processor using
isolcpus, preemp-rt and xenomai effectively future proof agains smi/chip
set issues (specificly AMD or Intel dual core solutions) by isolating a
cpu for exclusively xenomai/realtime use?
Some background information:
The realtime software I've developed in the past (with RTAI/adeos in
user space) is a simple high speed serializer driver (mmap) to
communicate with outside hardware and is responsible for syncronizing
(with a semaphore/mutex) a linux process (soft realtime) at ~60Hz. The
realtime process is periodic at 1.2Khz or 2.4Khz and calculates/filters
the data before sending commands back down the serializer interface and
to the linux process for soft realtime network access.
Generally we like to use "off the shelf" business PC's (Dell 170's and
Dell 270's, HP 5000 with 1Gig memory) and find that 20-30us latency is
achievable. We use "off the shelf" hardware because availability
(recieve within a week) and low cost are desired. Whenever looking for
an alernative solution either availablity or cost becomes a show
stopper. I'm open to suggestions and invite anyones thoughts on the
subject.
Thanks for your time !
JKS
next reply other threads:[~2006-02-09 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 17:49 John Schipper [this message]
2006-02-09 18:19 ` [Xenomai-core] Isolated CPU, SMI problems an thoughts Jan Kiszka
-- strict thread matches above, loose matches on Subject: below --
2006-02-09 20:16 John Schipper
2006-02-11 1:09 ` Max Krasnyansky
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=43EB80BC.1060403@domain.hid \
--to=jschipper@domain.hid \
--cc=xenomai@xenomai.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 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.