xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 1 of 3] Support of getting scheduler defaults
Date: Tue, 22 May 2012 14:58:58 +0200	[thread overview]
Message-ID: <4FBB8D92.8050800@ts.fujitsu.com> (raw)
In-Reply-To: <1337689975.10118.102.camel@zakaz.uk.xensource.com>

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
> value?

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

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

... 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

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

  reply	other threads:[~2012-05-22 12:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22  9:16 [PATCH 0 of 3] support of setting scheduler parameters on domain creation Juergen Gross
2012-05-22  9:16 ` [PATCH 1 of 3] Support of getting scheduler defaults Juergen Gross
2012-05-22 12:22   ` Ian Campbell
2012-05-22 12:29     ` Juergen Gross
2012-05-22 12:32       ` Ian Campbell
2012-05-22 12:58         ` Juergen Gross [this message]
2012-05-22 13:05           ` George Dunlap
2012-05-22 13:16             ` Ian Campbell
2012-05-22 13:40             ` Ian Campbell
2012-05-22 14:59               ` Ian Campbell
2012-05-22 23:46                 ` Dario Faggioli
2012-05-23  5:34                   ` Juergen Gross
2012-05-23  7:22                     ` Dario Faggioli
2012-05-23  7:41                       ` Ian Campbell
2012-05-23  8:45                         ` Juergen Gross
2012-05-23  9:17                           ` Ian Campbell
2012-05-23 10:18                           ` Dario Faggioli
2012-05-23  8:48                       ` Juergen Gross
2012-05-22  9:16 ` [PATCH 2 of 3] Support getting scheduler defaults in libxc Juergen Gross
2012-05-22  9:16 ` [PATCH 3 of 3] full support of setting scheduler parameters on domain creation Juergen Gross
2012-05-22 12:30   ` Ian Campbell
2012-05-22 12:39     ` Juergen Gross
2012-05-22 12:51       ` Ian Campbell
2012-05-22 22:15       ` Dario Faggioli

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=4FBB8D92.8050800@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --cc=Ian.Campbell@citrix.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).