From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dario Faggioli <dario.faggioli@citrix.com>
Subject: Re: xenpm and scheduler
Date: Tue, 12 Apr 2016 10:10:09 +0200
Message-ID: <1460448609.13871.104.camel@citrix.com>
References: <HE1PR05MB13085B6B44B6D1569333EB478D940@HE1PR05MB1308.eurprd05.prod.outlook.com>
 , <CAENZ-+mc6_N4p8NcYboA_5R0rw3+RQGtNfRoODEmWEhKJTwUcA@mail.gmail.com>
 <HE1PR05MB1308EB2B24B615D4E76CC2C28D950@HE1PR05MB1308.eurprd05.prod.outlook.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7701791324267211359=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <HE1PR05MB1308EB2B24B615D4E76CC2C28D950@HE1PR05MB1308.eurprd05.prod.outlook.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
 <mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
 <mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Errors-To: xen-devel-bounces@lists.xen.org
Sender: "Xen-devel" <xen-devel-bounces@lists.xen.org>
To: tutu sky <ooohooo_u@hotmail.com>, Meng Xu <xumengpanda@gmail.com>
Cc: "Xen-devel@lists.xen.org" <Xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

--===============7701791324267211359==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="=-h2AUzl7MW7tUDljlwJ/5"

--=-h2AUzl7MW7tUDljlwJ/5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, 2016-04-12 at 03:52 +0000, tutu sky wrote:
> Thanks Xu. I will do as desired about cross messaging.
>=20
> 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).
>=20
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?
>=20
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
--=20
<<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)


--=-h2AUzl7MW7tUDljlwJ/5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEABECAAYFAlcMrWEACgkQk4XaBE3IOsTIkACgqqIsMvjql8tAS8btzVPo2Nu/
kOUAn0zhHhd13HlLU2TQNb8y5tIClbCB
=9AVe
-----END PGP SIGNATURE-----

--=-h2AUzl7MW7tUDljlwJ/5--


--===============7701791324267211359==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs
IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9y
Zy94ZW4tZGV2ZWwK

--===============7701791324267211359==--