From: Dario Faggioli <raistlin@linux.it>
To: Juergen Gross <juergen.gross@ts.fujitsu.com>
Cc: George Dunlap <dunlapg@umich.edu>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH] full support of setting scheduler parameters on domain creation
Date: Tue, 22 May 2012 09:42:36 +0200 [thread overview]
Message-ID: <1337672556.20890.2.camel@Abyss> (raw)
In-Reply-To: <4FBB2775.30306@ts.fujitsu.com>
[-- Attachment #1.1: Type: text/plain, Size: 1186 bytes --]
On Tue, 2012-05-22 at 07:43 +0200, Juergen Gross wrote:
> Reading the scheduler parameters would require a new hypervisor interface
> (e.g. a new sub-command of XEN_DOMCTL_scheduler_op) which will have to be
> implemented by all schedulers supporting parameter changes.
>
> I think this would be the cleanest solution. If this is the way to go, I
> can prepare a patch.
>
For what it counts, this is what I'd like most.
> BTW: I just discovered the first patch was not complete, as the original
> coding to select the scheduler didn't take cpupools into account. It just
> selected the default scheduler instead of the cpupool specific one.
>
Yep, I noticed it too and mentioned on the list, but didn't have time
yet to cook a patch for that... I guess you're going to cover it while
reposting, aren't you? If not, let me know, I can put something
together. :-)
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/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:[~2012-05-22 7:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 11:46 [PATCH] full support of setting scheduler parameters on domain creation Juergen Gross
2012-05-21 12:07 ` Ian Campbell
2012-05-21 13:23 ` Juergen Gross
2012-05-21 13:34 ` Ian Campbell
2012-05-21 13:48 ` Juergen Gross
2012-05-21 13:48 ` George Dunlap
2012-05-21 13:53 ` Ian Campbell
2012-05-22 5:43 ` Juergen Gross
2012-05-22 7:42 ` Dario Faggioli [this message]
2012-05-22 7:47 ` Juergen Gross
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=1337672556.20890.2.camel@Abyss \
--to=raistlin@linux.it \
--cc=Ian.Campbell@citrix.com \
--cc=dunlapg@umich.edu \
--cc=juergen.gross@ts.fujitsu.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).