xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Rajendra Bele <belerajendra753@gmail.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	xen-devel@lists.xensource.com, Xen-devel@lists.xen.org
Subject: Re: xen scheduler
Date: Thu, 21 May 2015 11:57:28 +0200	[thread overview]
Message-ID: <1432202248.7907.29.camel@citrix.com> (raw)
In-Reply-To: <CAJRmKy_ryBuD5NzEt6mAE6sNsHqWUJh=SNAR64zmohH+Xb_Ecw@mail.gmail.com>


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

On Thu, 2015-05-21 at 13:25 +0530, Rajendra Bele wrote:
> Hi
> Dario,
>
Hi,

> Here Priority will be prime Method of Sorting of VCPUs in local run
> queue in addition to it I am Proposing Shortest Credit First
>  which is similar to SJF not exactly SJF of O.S. because this is
> credit based.
>
Understood. My point was that basing on credits will make the final
result rather different than SJF. That does not mean it won't work, of
course. :-)
> 
> My suggestion is Replace FCFS by SCF(Shortest Credit First) for Equal
> Priority VCPUs in local run-queue to reduce average waiting time spend
> in the queue.
>
I got that, and I tried to outline what possible issues I could think
to... but with this things, you never know until you try.
> 
> SCF will be preemptive but Credit Scheduler Itself preemptive after 30
> milliseconds
>
Sure it is. And in fact, right now, I'd say Credit is more Round-Robin
(there is a timeslice) than FCFS, in how it treats same priority vCPUs.
But let's not make this a "taxonomy bun fight"! :-P
> 
> As per my knowledge feature haven't implemented in credit2 also
>
Credit2 keeps its runqueue sorted already. Have a look, for instance, at
__runq_insert(), in sched_credit2.c. It's not SJF (nor it is this SCF
variant you're proposing), and I never said it to be... I've only said
having the runqueue sorted is, in general, a good thing, and Credit2
does this already.

However, generic arguments and assumptions tend not to work that great
in scheduling... we'll see how well that adapts to Credit1 when you'll
have it implemented. :-D
> 
> credit2 also sorts vcpus on priority and apply FCFS for equal
> priority .
>
As already said, check __runq_insert() and runq_tickle() in
xen/common/sched_credit2.c.

> Credit2 having dynamic time slice facility instead of fix 30
> milliseconds we can change 5,10,20 rest of things are as it is of
> credit1.
>
Credit2 has a much more dynamic timeslice than that. Check out
csched2_runtime().

Oh, and you may find useful having a look at these slides:
 http://www-archive.xenproject.org/files/xensummit_intel09/Xenschedulerstatus.pdf

and to this (3 part) video:
 https://www.youtube.com/watch?v=o4frC5bv3es
 https://www.youtube.com/watch?v=2ZAY9J-Cwsw
 https://www.youtube.com/watch?v=TQPVODqEkqM

Although, as usual, the best possible *source* of information is the
*source* code! :-D

Regards,
Dario


[-- 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

  reply	other threads:[~2015-05-21  9:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18  7:54 xen scheduler Rajendra Bele
2015-05-18 14:53 ` Dario Faggioli
2015-05-19  1:50   ` Rajendra Bele
2015-05-19  8:43     ` Dario Faggioli
2015-05-21  7:55       ` Rajendra Bele
2015-05-21  9:57         ` Dario Faggioli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-04-19 20:51 Xen scheduler David Xu
2011-04-20  8:47 ` George Dunlap
2007-10-24 19:55 xen scheduler Agarwal, Lomesh
2007-10-25 23:29 ` Atsushi SAKAI
2007-04-21  6:03 Xen scheduler pak333
2007-04-21  9:21 ` pradeep singh rautela
2007-04-22 13:09 ` Mike D. Day

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=1432202248.7907.29.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Xen-devel@lists.xen.org \
    --cc=belerajendra753@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).