xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
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: Wed, 13 Jan 2010 15:16:51 +0000	[thread overview]
Message-ID: <C7739463.648C%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <de76405a1001130648u50ccf3ebg3bde1b0c79840366@mail.gmail.com>

On 13/01/2010 14:48, "George Dunlap" <George.Dunlap@eu.citrix.com> wrote:

> The first implements something like what you suggest below, but
> instead of using a sort of "hack" with VPF_migrate, it makes a proper
> "context_saved" SCHED_OP callback.

I thought using the vcpu_migrate() path might work well since you presumably
have logic there to pick a new cpu which is relatively unloaded, making the
cpu which tried to schedule the vcpu but had to idle instead a prime
candidate. So rather than having to implement a new callback hook, you'd get
to leverage the pick_cpu hook for free?

> The second addresses the fact that when sharing runqueues,
> v->processor may change quickly without an explicit migrate.

I can't think of a better solution for this one.

 -- Keir

  reply	other threads:[~2010-01-13 15:16 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
2010-01-13 14:48       ` George Dunlap
2010-01-13 15:16         ` Keir Fraser [this message]
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=C7739463.648C%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).