All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Sisu Xi <xisisu@gmail.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: VCPU migration overhead conpensation ?
Date: Tue, 9 Apr 2013 03:46:40 +0200	[thread overview]
Message-ID: <1365472000.9958.110.camel@Solace> (raw)
In-Reply-To: <CAPqOm-pCJXGzX9ebkxy16oTp9P-Rk=41mgZywznWOm5VEn3XBw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1433 bytes --]

On ven, 2013-03-29 at 16:16 -0500, Sisu Xi wrote:
> Hi, all:
> 
Hi again Sisu,

> I am studying the credit2 scheduler and found it would compensate VCPU
> migration with 50 microseconds.
> /* How much to "compensate" a vcpu for L2 migration */
> #define CSCHED_MIGRATE_COMPENSATION MICROSECS(50)
> 
> 
> Why 50us? Is this number based on some experiments? 
>
This predates my joining of the Xen community, but yes, ISTR hearing
people talking about it coming from a mixture of common sense and
experience/measurements.

BTW, you may want to try, when sending e-mail to this list, adding in Cc
some of the people that are more involved with the code/feature you're
asking about. You can look at the MAINTAINERS file, in the source tree,
to have an idea of who to put there. For instance, for scheduling, the
absolute authority is George (which I added), and in fact MAINTAINERS
says: 

SCHEDULING
M:      George Dunlap <george.dunlap@eu.citrix.com>
S:      Supported
F:      xen/common/sched*

(however, feel free to Cc me as well... I do not master all the Xen
scheduler code yet, but am always curious about it. :-) )

Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-04-09  1:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29 21:16 VCPU migration overhead conpensation ? Sisu Xi
2013-04-09  1:46 ` Dario Faggioli [this message]
2013-04-10  5:44   ` Sisu Xi
2013-04-10  6:53     ` Dario Faggioli
2013-04-10  8:21     ` George Dunlap
2013-04-10  8:25       ` Dario Faggioli
2013-04-10 18:58         ` Sisu Xi

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=1365472000.9958.110.camel@Solace \
    --to=dario.faggioli@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xisisu@gmail.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.