From: NISHIGUCHI Naoki <nisiguti@jp.fujitsu.com>
To: "Su, Disheng" <disheng.su@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"sakaia@jp.fujitsu.com" <sakaia@jp.fujitsu.com>,
"aviv@neocleus.com" <aviv@neocleus.com>,
"Ian.Pratt@eu.citrix.com" <Ian.Pratt@eu.citrix.com>,
"keir.fraser@eu.citrix.com" <keir.fraser@eu.citrix.com>
Subject: Re: RE: [RFC][PATCH 0/4] Modification of credit scheduler rev2
Date: Thu, 15 Jan 2009 14:19:15 +0900 [thread overview]
Message-ID: <496EC753.1070805@jp.fujitsu.com> (raw)
In-Reply-To: <BB1F052FCDB1EA468BD99786C8B1ED2C01D264C62E@PDSMSX501.ccr.corp.intel.com>
Su, Disheng wrote:
> NISHIGUCHI Naoki wrote:
>>> c. the limitation of weight for guest B. I have to set the weight
>>> of guest B to 10. It may not be reasonable in real usage case.
>> Is copying large files in background on guest A indispensable?
>> In my test, guest A runs only video playing.
>> I think that my approach couldn't solve this issue.
>
> You know, guest A is the primary guest to end user, so we can't make any assumption about the user's operation in guest A, which is the big challenge for client virtualization IMO.
> Weight, Cap, Boost credit, are all can be used together, or adding new mechanism, such as static priority as Kevin said, to solve the problem.
I see.
That is really the big challenge.
I think we should experiment in various configuration and clarify some
problems.
>>> Do you have the experience with audio? I don't know I have properly
>>> configured your scheduler or not. Hope the your scheduler can solve
>>> the audio issues also.
>> Sorry, I don't have the experience with audio.
>> But I'll try to reproduce your configuration and investigate.
>>
>
> Glad to see you have interest with audio also. Any problem when you reproduce the audio issues, pls let me know.
Thanks.
Regards,
Naoki
prev parent reply other threads:[~2009-01-15 5:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 2:57 [RFC][PATCH 0/4] Modification of credit scheduler rev2 NISHIGUCHI Naoki
2008-12-18 3:00 ` [RFC][PATCH 1/4] sched: more accurate credit scheduling NISHIGUCHI Naoki
2008-12-18 3:02 ` [RFC][PATCH 2/4] sched: change the handling of credits over upper bound NISHIGUCHI Naoki
2008-12-18 3:04 ` [RFC][PATCH 3/4] sched: balance credits of each vcpu of a domain NISHIGUCHI Naoki
2008-12-18 3:06 ` [RFC][PATCH 4/4] sched: introduce boost credit for latency-sensitive domain NISHIGUCHI Naoki
2009-01-13 8:10 ` [RFC][PATCH 0/4] Modification of credit scheduler rev2 Su, Disheng
2009-01-15 2:04 ` NISHIGUCHI Naoki
2009-01-15 2:56 ` Tian, Kevin
2009-01-15 4:42 ` NISHIGUCHI Naoki
2009-01-15 5:04 ` Tian, Kevin
2009-01-15 6:05 ` NISHIGUCHI Naoki
2009-01-15 6:41 ` Tian, Kevin
2009-01-15 7:01 ` NISHIGUCHI Naoki
2009-01-15 7:04 ` Tian, Kevin
2009-01-15 4:55 ` Su, Disheng
2009-01-15 5:19 ` NISHIGUCHI Naoki [this message]
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=496EC753.1070805@jp.fujitsu.com \
--to=nisiguti@jp.fujitsu.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Pratt@eu.citrix.com \
--cc=aviv@neocleus.com \
--cc=disheng.su@intel.com \
--cc=keir.fraser@eu.citrix.com \
--cc=sakaia@jp.fujitsu.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.