From: Dario Faggioli <dario.faggioli@citrix.com>
To: Massimo Canonico <mex@di.unipmn.it>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Ian Jackson <ian.jackson@citrix.com>,
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:48:48 +0200 [thread overview]
Message-ID: <1371026928.20028.58.camel@Solace> (raw)
In-Reply-To: <51B7431F.2080006@di.unipmn.it>
[-- Attachment #1.1: Type: text/plain, Size: 526 bytes --]
On mar, 2013-06-11 at 17:32 +0200, Massimo Canonico wrote:
> Thanks.
> I was expecting that this warning appears somewhere here:
> http://wiki.xen.org/wiki/Credit_Scheduler#Cap
>
> but I did not find it.
>
I just added it there too.
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
next prev parent reply other threads:[~2013-06-12 8:48 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 [this message]
2013-06-12 8:41 ` Dario Faggioli
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=1371026928.20028.58.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 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).