All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Dieter Bloms <dieter@bloms.de>
Cc: Dario Faggioli <dario.faggioli@citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Fantu <fantonifabio@tiscali.it>
Subject: Re: Test result of xen-unstable changeset 25249
Date: Fri, 27 Apr 2012 09:44:41 +0100	[thread overview]
Message-ID: <4F9A5C79.2090604@eu.citrix.com> (raw)
In-Reply-To: <20120427082114.GA28258@bloms.de>

On 27/04/12 09:21, Dieter Bloms wrote:
> yes, this is an issue with my patch :( All default values has to be 0, 
> but only for the credit(2) scheduler cpu_weight must not. So I made a 
> patch, which set a default of 256 when the cpu_weight isn't set and 
> credit(2) is used and let it 0 when the scheduler sedf is used. Please 
> try the attached patch and see if it solve this issue. 
Dieter,

Thanks for the patch.  However, I'd really rather avoid putting 
scheduler defaults in xl if we can at all avoid it.  Defaults should be 
set in one place, and that should be in the scheduling code itself.

I think what we really want to do is is any of the parameters are set, 
after the domain is first created, to read the scheduling parameters for 
the domain (which will be the defaults), change the ones that are set in 
the config file, and then write the whole structure back.  That 
shouldn't be too hard, as libxl__sched_set_params() is called after the 
domain itself is created; the main thing is how to tell 
libxl__sched_set_params() which parameters actually need to be set, and 
which should be left alone.

Are you up for doing that?  If not, I can put it on my to-do list.

Thanks,
  -George

  reply	other threads:[~2012-04-27  8:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 10:26 Test result of xen-unstable changeset 25249 Fantu
2012-04-26 11:55 ` Ian Campbell
2012-04-26 12:06   ` Fantu
2012-04-26 13:49     ` Ian Campbell
2012-04-26 13:57       ` Fantu
2012-04-26 14:21         ` Ian Campbell
2012-04-27  8:21   ` Dieter Bloms
2012-04-27  8:44     ` George Dunlap [this message]
2012-04-27  9:08       ` Ian Campbell
2012-04-27 12:15         ` Fantu
2012-04-27 13:19           ` Ian Campbell
2012-04-27 14:27             ` Fantu
2012-04-27 14:36               ` Ian Campbell
2012-04-30  8:37                 ` Fantu
2012-04-30  9:10                   ` Fantu
2012-04-27 15:20         ` Dario Faggioli
2012-04-27 15:28           ` Ian Campbell
2012-04-27 15:35             ` Dario Faggioli
2012-04-27 15:38               ` Ian Campbell

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=4F9A5C79.2090604@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=dario.faggioli@citrix.com \
    --cc=dieter@bloms.de \
    --cc=fantonifabio@tiscali.it \
    --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 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.