All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: tutu sky <ooohooo_u@hotmail.com>, Meng Xu <xumengpanda@gmail.com>
Cc: "Xen-devel@lists.xen.org" <Xen-devel@lists.xen.org>
Subject: Re: xenpm and scheduler
Date: Tue, 12 Apr 2016 10:10:09 +0200	[thread overview]
Message-ID: <1460448609.13871.104.camel@citrix.com> (raw)
In-Reply-To: <HE1PR05MB1308EB2B24B615D4E76CC2C28D950@HE1PR05MB1308.eurprd05.prod.outlook.com>


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

On Tue, 2016-04-12 at 03:52 +0000, tutu sky wrote:
> Thanks Xu. I will do as desired about cross messaging.
> 
> i need it because i exactly want to know that which part of the
> scheduler's corde (credit), takes effect from this feature. because
> it is important to me knowing that where would be trade off between
> idle state and doing load balancing, while cpuidle feature is
> activated. in other side it's important again for me that what will
> happen for 'cap; and 'weight' decreasing in a case that one core's
> frequency is lower than another one in the same socket (actually when
> cpufreq feature is enable).
> 
Currently, there is no interaction between the scheduler and the power
management and frequency scaling layers.

> Am i clear enough? can you give me an answer or maybe some lines of
> schedule.c or sched_credit.c's code which i can track them to notice
> the effect of xenpm on scheduler part of the view?
> 
If you're saying that, for instance, the CPUs changing frequency can or
should affect some aspects of the scheduling algorithms (like credits
burning rate in Credit1 and Credit2, and budget burning rate in RTDS),
that is an interesting point which may indeed make sense, or at least
would deserve more investigation.

But again, right now, there's no line of code to read to understand the
relationship, as there's no relationship at all.

If you want to experiment on playing with xenpm, and seeing what effect
it has on scheduling, that will be very welcome. :-)

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

  reply	other threads:[~2016-04-12  8:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11  8:16 xenpm and scheduler tutu sky
2016-04-11 12:11 ` Meng Xu
2016-04-12  3:52   ` tutu sky
2016-04-12  8:10     ` Dario Faggioli [this message]
2016-04-12 11:50       ` tutu sky
2016-04-12 13:41         ` Konrad Rzeszutek Wilk
2016-04-12 17:04           ` tutu sky
2016-04-12 17:08             ` Konrad Rzeszutek Wilk
2016-04-12 17:46               ` tutu sky
2016-04-12 21:05                 ` Dario Faggioli
2016-04-13  8:21                   ` tutu sky
2016-04-13  9:52                     ` Konrad Rzeszutek Wilk
2016-04-13 10:24                     ` Dario Faggioli

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=1460448609.13871.104.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=Xen-devel@lists.xen.org \
    --cc=ooohooo_u@hotmail.com \
    --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.