From: George Dunlap <george.dunlap@eu.citrix.com>
To: Meng Xu <xumengpanda@gmail.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Dario Faggioli <dario.faggioli@citrix.com>,
Tim Deegan <tim@xen.org>,
Denys Drozdov <denys.drozdov@globallogic.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Linh Thi Xuan Phan <linhphan@cis.upenn.edu>,
Insup Lee <lee@cis.upenn.edu>, Jan Beulich <JBeulich@suse.com>,
"andrii.tseglytskyi@globallogic.com"
<andrii.tseglytskyi@globallogic.com>
Subject: Re: Design and Question: Eliminate Xen (RTDS) scheduler overhead on dedicated CPU
Date: Wed, 25 Mar 2015 13:52:16 +0000 [thread overview]
Message-ID: <5512BD90.9020500@eu.citrix.com> (raw)
In-Reply-To: <CAENZ-+mxadcuePxQsozqFM1M7ZAeNFyWkHqYKhEx1Q2FhFT3FA@mail.gmail.com>
On 03/25/2015 01:50 PM, Meng Xu wrote:
> 2015-03-25 7:58 GMT-04:00 George Dunlap <george.dunlap@eu.citrix.com>:
>
>> On 03/25/2015 01:48 AM, Meng Xu wrote:
>>> Exactly! I will do some measurement on the overhead in #2 before I
>> really
>>> try to do it. Since #1 is fairly easy, I will first implement #1 and see
>>> how much gap it remains to achieve the bare-metal performance.
>>
>> Interface-wise: I'm wondering if at the Xen or libxl level we really
>> need to have a whole new set of hypercalls, at least to implement #1.
>> Would it make sense for certain schedulers to automatically switch to
>> "no accounting" mode when the hard_affinity of a vcpu is limited to one
>> vcpu, and no other vcpus are also limited to that one vcpu?
>>
>
> I guess you mean:
> certain schedulers to automatically switch to
> "no accounting" mode when the hard_affinity of a vcpu is limited to one
> "
> cpu
> " (not vcpu)
> , and
>
> no other vcpus are also limited to that one
> "
> cpu
> "
> ?
>
> Am I correct? :-)
Ah, yes, thanks. :-)
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-03-25 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 3:50 Design and Question: Eliminate Xen (RTDS) scheduler overhead on dedicated CPU Meng Xu
2015-03-24 11:54 ` George Dunlap
2015-03-24 15:27 ` Meng Xu
2015-03-24 21:08 ` George Dunlap
2015-03-25 1:48 ` Meng Xu
2015-03-25 11:58 ` George Dunlap
2015-03-25 13:50 ` Meng Xu
2015-03-25 13:52 ` George Dunlap [this message]
2015-03-25 18:50 ` Konrad Rzeszutek Wilk
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=5512BD90.9020500@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrii.tseglytskyi@globallogic.com \
--cc=dario.faggioli@citrix.com \
--cc=denys.drozdov@globallogic.com \
--cc=lee@cis.upenn.edu \
--cc=linhphan@cis.upenn.edu \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=xumengpanda@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.