From: "Stephan Diestelhorst" <sd386@cl.cam.ac.uk>
To: xen-devel@lists.sourceforge.net
Subject: Re: atropos still broken?
Date: Fri, 28 Jan 2005 08:08:35 -0000 [thread overview]
Message-ID: <00a501c50511$f3abc270$f236a8c0@jgaarder> (raw)
In-Reply-To: 200501280243.17987.maw48@cl.cam.ac.uk
> > So it seems atropos is still broken. Is a fix being worked upon? I'd
>
> Fixing Atropos is still on my todo list. One of the other developers is
> working on an alternative deadline-based scheduler, which may behave
better.
>
Indeed, that's me :) My scheduler is working quite well, but I want to do
some testing/benchmarking today before it gets released to the "wild"...
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
prev parent reply other threads:[~2005-01-28 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 4:25 atropos still broken? Diwaker Gupta
2005-01-27 9:02 ` Steven Hand
2005-01-27 22:11 ` Gregor Milos
2005-01-28 2:43 ` Mark Williamson
2005-01-28 8:08 ` Stephan Diestelhorst [this message]
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='00a501c50511$f3abc270$f236a8c0@jgaarder' \
--to=sd386@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.