All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: Ian Jackson <ian.jackson@citrix.com>,
	Massimo Canonico <mex@di.unipmn.it>,
	Ian Campbell <ian.campbell@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH] docs: Make note for the scheduler "cap" option warning about power management effects
Date: Wed, 12 Jun 2013 10:41:23 +0200	[thread overview]
Message-ID: <1371026483.20028.57.camel@Solace> (raw)
In-Reply-To: <1370953898-10278-1-git-send-email-george.dunlap@eu.citrix.com>


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

On mar, 2013-06-11 at 13:31 +0100, George Dunlap wrote:
> Suggested-by: Massimo Canonico <mex@di.unipmn.it>
> Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
> CC: Ian Campbell <ian.campbell@citrix.com>
> CC: Ian Jackson <ian.jackson@citrix.com>
> CC: Massimo Canonico <mex@di.unipmn.it>
>
Reviewed-by: Dario Faggioli <dario.faggioli@citrix.com>

> ---
>  docs/man/xl.cfg.pod.5 |   13 +++++++++++++
>  docs/man/xl.pod.1     |   13 +++++++++++++
>  docs/man/xm.pod.1     |   13 +++++++++++++
>  3 files changed, 39 insertions(+)
> 
> diff --git a/docs/man/xl.cfg.pod.5 b/docs/man/xl.cfg.pod.5
> index b7d64a6..069b73f 100644
> --- a/docs/man/xl.cfg.pod.5
> +++ b/docs/man/xl.cfg.pod.5
> @@ -153,6 +153,19 @@ The cap is expressed in percentage of one physical CPU:
>  The default, 0, means there is no upper cap.
>  Honoured by the credit and credit2 schedulers.
>  
> +NB: Many systems have features that will scale down the computing
> +power of a cpu that is not 100% utilized.  This can be in the
> +operating system, but can also sometimes be below the operating system
> +in the BIOS.  If you set a cap such that individual cores are running
> +at less than 100%, this may have an impact on the performance of your
> +workload over and above the impact of the cap. For example, if your
> +processor runs at 2GHz, and you cap a vm at 50%, the power management
> +system may also reduce the clock speed to 1GHz; the effect will be
> +that your VM gets 25% of the available power (50% of 1GHz) rather than
> +50% (50% of 2GHz).  If you are not getting the performance you expect,
> +look at performance and cpufreq options in your operating system and
> +your BIOS.
> +
>
I'd have been less 'politically correct' toward BIOSes, but I guess
that's me! :-P

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: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  parent reply	other threads:[~2013-06-12  8:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 12:31 [PATCH] docs: Make note for the scheduler "cap" option warning about power management effects George Dunlap
2013-06-11 15:32 ` Massimo Canonico
2013-06-12  8:48   ` Dario Faggioli
2013-06-12  8:41 ` Dario Faggioli [this message]
2013-06-12  9:44 ` Ian Campbell
2013-06-12  9:58   ` Dario Faggioli
2013-06-12 13:57 ` Konrad Rzeszutek Wilk
2013-06-12 14:59   ` Ian Campbell
2013-06-12 15:01     ` George Dunlap
2013-06-14 18:38       ` Konrad Rzeszutek Wilk

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=1371026483.20028.57.camel@Solace \
    --to=dario.faggioli@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=mex@di.unipmn.it \
    --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.