From: "michaeli.zhi" <michaeli.zhi@gmail.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: The overhead of VCPu migration in xen
Date: Fri, 20 Nov 2009 15:26:28 +0800 [thread overview]
Message-ID: <200911201526244379262@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 618 bytes --]
Hi, everyone.
I did a little study on the code of credit scheduler of xen.
I am confused on overhear of the migration of VCPU .
As I learned, the course of VCPU migration is just to return a "reasonable" VCPU of other peer PCPU
to the PCPU which is busy on other VCPU, as well as some judgments before(eg., comparision of VCPU priority, affintiy).
In a word, it is just a pointer returned.
My question is where is the overhead,
or the overhead of executing those load_balance codes is expensive,
or will the migration of VCPU introducing the somekind of cache failure?
Best regards
2009-11-20
michaeli.zhi
[-- Attachment #1.2: Type: text/html, Size: 1453 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2009-11-20 7:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200911201526244379262@gmail.com \
--to=michaeli.zhi@gmail.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 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.