From: Holger Steinhaus <hsteinhaus@gmx.de>
To: xen-devel@lists.xensource.com
Subject: realtime scheduling
Date: Mon, 08 Aug 2005 17:06:56 +0200 [thread overview]
Message-ID: <42F77510.5070501@gmx.de> (raw)
Hi everyone,
I am trying to set up an ISDN gateway and PBX system and want to use Xen
to seperate some components against each other. Unfortunatly, a
necessary device driver (zaphfc) depends on very short latencys for
servicing interrupts. This driver is located in domain0 and everything
runs fine, as long as all other domains are idling. If the guests get
something to do, the zaphfc driver suffers massive buffer under/overflow
problems.
I've found some hints about the Atropos realtime scheduler on the list,
but some posts say, it is broken currently.
1.) Are there any releases with a working RT-like scheduler?
2.) Do you have any other idea to minimize the scheduling-related
latency for domain 0?
Thanks,
Holger
next reply other threads:[~2005-08-08 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 15:06 Holger Steinhaus [this message]
2005-08-08 15:25 ` realtime scheduling Keir Fraser
2005-08-08 17:16 ` Stephan Diestelhorst
2005-08-08 21:11 ` Holger Steinhaus
2005-08-09 7:27 ` Keir Fraser
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=42F77510.5070501@gmx.de \
--to=hsteinhaus@gmx.de \
--cc=xen-devel@lists.xensource.com \
/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.