All of lore.kernel.org
 help / color / mirror / Atom feed
From: xuehai zhang <hai@cs.uchicago.edu>
To: Stephan Diestelhorst <sd386@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: atropos again
Date: Thu, 05 May 2005 11:51:09 -0500	[thread overview]
Message-ID: <427A4EFD.1000105@cs.uchicago.edu> (raw)
In-Reply-To: <427A14BB.9090801@cl.cam.ac.uk>

Stephan,

Thanks for the response.

>>>>BTW, Could anyone answer my question aobut the current status of Atropos
>>>>scheduler I sent a couple of days ago
>>>
>>>I've ported the scheduler to the unstable tree, and it will hopefully
>>>get checked in in the near future! (*prod*)
>>
>>
>>The scheduler you mean is the atropos replacement you develop or just
>>atropos? If it is the former, what is the name of the replacement? Can I
>>just use "sched=<name>" as what I use for other scheduler to enable it?
>>Sinced it has been ported to the unstable tree, can I assume the testing
>>tree has been ported as well?
> 
> 
> It is quite versatile, you can compile it so that it just does Atropos,
> but it can do much more ;-) The current name for the thing is 'sedf'
> which originated from Simple-EDF, but probably it's time now to call it
> 'Smart-EDF' or come up with a more reasonable name in general!
> 
> As it is not yet in the repositories you can't use it though...


> ATM there is also a version for the testing tree, but as I said they are
> not in the main repos yet.

To clarify: even if I use "bk clone bk://xen.bkbits.net/xen-2.0-testing.bk" to get the latest 
testing tree, I will not find sedf scheduler because it has not been included yet.

It is still unclear to me if Atropos scheduler in the above testing tree works correctly or still 
buggy as pointed out by previous posts 2 month ago.

Thanks again for your help.

Xuehai

> Cheers,
>    Stephan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 

  reply	other threads:[~2005-05-05 16:51 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
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 [this message]
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=427A4EFD.1000105@cs.uchicago.edu \
    --to=hai@cs.uchicago.edu \
    --cc=sd386@cl.cam.ac.uk \
    --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.