All of lore.kernel.org
 help / color / mirror / Atom feed
From: xuehai zhang <hai@cs.uchicago.edu>
To: xuehai zhang <hai@cs.uchicago.edu>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: atropos again
Date: Wed, 04 May 2005 15:53:04 -0500	[thread overview]
Message-ID: <42793630.4050602@cs.uchicago.edu> (raw)
In-Reply-To: <4276A399.7060304@cs.uchicago.edu>

Hi,
Is there anyway (some command I type in the commandline) I can find which scheudler is currently 
used by Xen?
BTW, Could anyone answer my question aobut the current status of Atropos scheduler I sent a couple 
of days ago?
Many thanks.
Xuehai

xuehai zhang wrote:
> Hi all,
> I read the previous threads in the mailing list (I attached Ross's post 
> sent on 2/23/05) about atropos scheduler and it looks to me the bug in 
> atropos has not been fixed until that time. Because I could not find any 
> new posts talking about atropos, I appreciate if anyone can update me 
> the current status of the atropos scheduler.
> BTW, Ross also mentioned Stephan is working on an alternative scheduler 
> and I wonder where I can get the patch or is it already included in the 
> latest version of Xen?
> Thank you so much for your help.
> Xuehai
> 
> 
>  > Hi,
>  >
>  > I am working on a project which requires enforced CPU partitioning
>  > between domains, and so was planning to use the atropos scheduler.
>  > However I notice from a previous post that atropos does not seem to be
>  > working.  Has there been any progress in finding the bug?
>  >
>  > I also noticed that Stephan Diestelhorst was working on an alternative
>  > deadline-based scheduler.  Is this ready for use?
>  >
>  >
>  > Thanks for your help
>  >
>  > Ross
>  >
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 

  reply	other threads:[~2005-05-04 20:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02 22:03 atropos again xuehai zhang
2005-05-04 20:53 ` xuehai zhang [this message]
2005-05-05  0:14   ` Stephan Diestelhorst
2005-05-05  0:50     ` Xuehai Zhang
2005-05-05 12:42       ` Stephan Diestelhorst
2005-05-05 16:51         ` xuehai zhang
2005-05-05 20:55           ` Stephan Diestelhorst
     [not found]             ` <427AD31D.5080502@cs.uchicago.edu>
     [not found]               ` <200505091153.01081.sd386@cam.ac.uk>
     [not found]                 ` <Pine.LNX.4.58.0505091225150.16644@rory.cs.uchicago.edu>
2005-05-10 21:18                   ` Stephan Diestelhorst
2005-05-11  1:45                     ` Xuehai Zhang
2005-05-11 10:28                       ` Stephan Diestelhorst

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=42793630.4050602@cs.uchicago.edu \
    --to=hai@cs.uchicago.edu \
    --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.