[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 1 of 3] Support of getting scheduler defaults

  • To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
  • From: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
  • Date: Tue, 22 May 2012 14:58:58 +0200
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 22 May 2012 12:59:23 +0000
  • Domainkey-signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:Message-ID:Date:From:Organization: User-Agent:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=r7UCg5hybJJemOp6211F49FHdRTXhrCsW1LfpLxxppGx85jTQHuSstcc zKT2LmtY9CXIlGec2nk/XrBHXXpsRfyifL1fE4IyayX61eD+o5OB15/TY 1IAOA8EqVbm+H9OPsay5S5x6bUPly440GKDQoOHQ9cfMxsRStGJufx9j1 NkHF1264pH6vS81N7ve1V9noaaMQ1qcX6BPTqwIdPJBkaD1o8hXsKzVdk qyAEY0qY7gM9DFZKlTbyO3G9OvV+K;
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 05/22/2012 02:32 PM, Ian Campbell wrote:
On Tue, 2012-05-22 at 13:29 +0100, Juergen Gross wrote:
On 05/22/2012 02:22 PM, Ian Campbell wrote:
On Tue, 2012-05-22 at 10:16 +0100, Juergen Gross wrote:
Support a new sysctl schedop sub-command to get the scheduling defaults of a
specific scheduler.
Why is XEN_DOMCTL_SCHEDOP_getinfo not sufficient here?

Isn't it actually more useful/meaningful to get the current actual
setting rather than a default?
When setting the parameters from the config file we have no domain yet which
we would have to specify for XEN_DOMCTL_SCHEDOP_getinfo. I didn't want to
parse part of the config only after domain creation.
That seems like another problem with doing this up front instead of
doing read-modify-write when we come to set the values for the domain.

Do you think it would be okay to parse the scheduler config data _after_
domain creation? If yes, the read-modify-write approach is simple and always
correct. If no, you will have to initialize the parameters to something
scheduler specific, and not domain specific.

A default should be okay, as this is what we want to modify. :-)
The scheduler should initialize a new domain with this default, of course.
So I can't use this interface to change the current one of the current
settings for running a domain, while leaving the others at their current

I don't understand this sentence :-) ...

Which interface can I use for that and why isn't it the same as this

... making it hard to answer to this one. :-)
Nevertheless trying: you can change the scheduling parameters of a running
domain with xl sched-credit/sched-sedf/...


Juergen Gross                 Principal Developer Operating Systems
PDG ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@xxxxxxxxxxxxxx
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.