From: Keir Fraser <keir.fraser@eu.citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: [PATCH] [RFC] Credit2 scheduler prototype
Date: Tue, 08 Dec 2009 18:20:53 +0000 [thread overview]
Message-ID: <C7444985.3E6A%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <de76405a0912080648r4fc91cf9v876682a5383ac654@mail.gmail.com>
On 08/12/2009 14:48, "George Dunlap" <George.Dunlap@eu.citrix.com> wrote:
> My main concern is that sharing the runqueue between cores requires
> some changes to the core context switch code. The kinks aren't 100%
> worked out yet, so there's a risk that there will be an impact on the
> correctness of the credit1 scheduler.
Ah, if that's the problem with selecting a vcpu which happens to still be
'is_running' then I had some ideas how you could deal with that within the
credit2 scheduler. If you see such a vcpu when searching the runqueue,
ignore it, but set VPF_migrating. You'll then get a 'pick_cpu' callback when
descheduling of the vcpu is completed. That should play nice with the lazy
context switch logic while keeping things work conserving.
-- Keir
next prev parent reply other threads:[~2009-12-08 18:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 17:02 [PATCH] [RFC] Credit2 scheduler prototype George Dunlap
2009-12-07 17:45 ` Keir Fraser
2009-12-08 14:48 ` George Dunlap
2009-12-08 18:20 ` Keir Fraser [this message]
2010-01-13 14:48 ` George Dunlap
2010-01-13 15:16 ` Keir Fraser
2010-01-13 16:05 ` George Dunlap
2010-01-13 16:36 ` Keir Fraser
2010-01-13 16:43 ` George Dunlap
2010-01-28 23:27 ` Dulloor
2010-01-29 0:56 ` George Dunlap
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=C7444985.3E6A%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=George.Dunlap@eu.citrix.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).