From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <dunlapg@umich.edu>, suokun <suokunstar@gmail.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [BUG] mistakenly wake in Xen's credit scheduler
Date: Tue, 27 Oct 2015 10:53:39 +0100 [thread overview]
Message-ID: <1445939619.2937.55.camel@citrix.com> (raw)
In-Reply-To: <CAFLBxZYyGpoftGbnGpiVbAFFT8m3Ctq9vOfMOfRSnWEW-mRs8w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1486 bytes --]
On Tue, 2015-10-27 at 09:44 +0000, George Dunlap wrote:
> On Tue, Oct 27, 2015 at 5:59 AM, suokun <suokunstar@gmail.com> wrote:
> > Hi all,
> >
> > The BOOST mechanism in Xen credit scheduler is designed to
> > prioritize
> > VM which has I/O-intensive application to handle the I/O request in
> > time. However, this does not always work as expected.
>
> Thanks for the exploration, and the analysis.
>
Yep, indeed. :-)
> The BOOST mechanism is part of the reason I began to write the
> credit2
> scheduler, which we are hoping (any day now) to make the default
> scheduler. It was designed specifically with the workload you
> mention
> in mind.
>
The whole BOOST thing is an hack, and I don't have much problems
believing it interacts poorly with the tickling mechanism, which, in
Credit1, is not very precise and reliable (e.g., in Credit2, there is a
'tickled' mask).
That being said, I'm looking at the analysis itself, and I'm not sure I
understand what exactly you are suggesting it's going on... I will
reply shortly with a few questions.
> Would you care to try your test again and see how it fares?
>
Well, that would be a lot useful, for sure! :-D
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: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-10-27 9:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 5:59 [BUG] mistakenly wake in Xen's credit scheduler suokun
2015-10-27 9:44 ` George Dunlap
2015-10-27 9:53 ` Dario Faggioli [this message]
2015-10-27 20:11 ` suokun
2015-10-28 5:39 ` suokun
2015-10-28 5:54 ` Dario Faggioli
2015-10-28 6:01 ` Juergen Gross
2015-10-28 6:08 ` Dario Faggioli
2015-10-28 11:03 ` George Dunlap
2015-10-27 10:44 ` Dario Faggioli
2015-10-27 20:32 ` suokun
2015-10-28 5:41 ` Dario Faggioli
2015-10-28 17:04 ` suokun
2015-10-29 10:25 ` Dario Faggioli
-- strict thread matches above, loose matches on Subject: below --
2015-10-26 22:30 Kun Suo
2015-10-27 5:48 ` Jia Rao
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=1445939619.2937.55.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=dunlapg@umich.edu \
--cc=suokunstar@gmail.com \
--cc=xen-devel@lists.xen.org \
/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.