From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Juergen Gross <juergen.gross@ts.fujitsu.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Kathy Hadley <Kathy.Hadley@dornerworks.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add support for CPU pools)
Date: Thu, 17 Jun 2010 07:09:04 +0100 [thread overview]
Message-ID: <C83F7A90.17B73%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4C19AC64.7090001@ts.fujitsu.com>
On 17/06/2010 06:02, "Juergen Gross" <juergen.gross@ts.fujitsu.com> wrote:
>> Oh yes, that was the old behaviour. I took a hatchet to the
>> scheduler/cpupool interfaces a few weeks ago and now we should only
>> initialise the scheduler once, unless extra cpupools are manually created.
>
> Keir, what do you think about creating an "idle-scheduler" for the cpus not in
> any cpupool? It would only schedule the idle vcpu and could be VERY minimal.
> This could reduce the complexity of moving cpus from and to cpupools.
>
> I could try to setup a patch if you support this idea (I'm asking for your
> opinion before starting this, as I'm rather busy with other tasks).
What we have now is fine (which is, basically, cpupool0 and the 'no-cpupool'
schedulers are one and the same thing). I don't want yet another scheduler
thanks. ;-)
-- Keir
prev parent reply other threads:[~2010-06-17 6:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 15:04 [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add support for CPU pools) Kathy Hadley
2010-06-16 15:50 ` George Dunlap
2010-06-16 16:00 ` Kathy Hadley
2010-06-16 16:13 ` Keir Fraser
2010-06-16 16:14 ` George Dunlap
2010-06-16 16:20 ` Keir Fraser
2010-06-16 16:25 ` Kathy Hadley
2010-06-16 16:31 ` Keir Fraser
2010-06-16 16:40 ` Kathy Hadley
2010-06-16 16:49 ` Keir Fraser
2010-06-16 18:03 ` Kathy Hadley
2010-06-17 7:04 ` Keir Fraser
2010-06-17 18:16 ` Kathy Hadley
2010-06-17 18:26 ` Keir Fraser
2010-06-18 17:35 ` Kathy Hadley
2010-06-18 17:49 ` Keir Fraser
2010-06-19 11:14 ` George Dunlap
2010-06-22 19:10 ` Kathy Hadley
2010-06-22 19:16 ` Keir Fraser
2010-06-23 19:57 ` Kathy Hadley
2010-06-23 20:23 ` Keir Fraser
2010-06-23 21:16 ` Kathy Hadley
2010-06-23 22:36 ` Keir Fraser
2010-06-24 12:53 ` Kathy Hadley
2010-06-24 13:08 ` Dan Magenheimer
2010-06-24 13:18 ` Kathy Hadley
2010-06-24 13:23 ` Keir Fraser
2010-06-24 13:32 ` Kathy Hadley
2010-06-30 20:44 ` Kathy Hadley
2010-06-30 20:54 ` Keir Fraser
2010-07-14 17:32 ` Kathy Hadley
2010-07-14 18:04 ` Keir Fraser
2010-06-16 16:25 ` George Dunlap
2010-06-17 5:02 ` Juergen Gross
2010-06-17 6:09 ` Keir Fraser [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=C83F7A90.17B73%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Kathy.Hadley@dornerworks.com \
--cc=juergen.gross@ts.fujitsu.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).