All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xen: Implement domain runstates
Date: Thu, 25 Nov 2010 22:10:57 +0000	[thread overview]
Message-ID: <C9148F71.B223%keir@xen.org> (raw)
In-Reply-To: <19694.46299.660998.230181@mariner.uk.xensource.com>

On 25/11/2010 19:11, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:

> George Dunlap writes ("Re: [Xen-devel] [PATCH] xen: Implement domain
> runstates"):
>> I wouldn't offer to put it in xentop just because I wanted to get the
>> patch out of the patchqueue.  I think it's a useful feature, that many
>> people would use if they knew about it.  If I didn't think it was
>> useful, by far the simplest way to get it out of the patchqueue would be
>> to simply remove the functionality from the next release of XenServer.
> 
> FWIW I think this sounds like a useful thing to have in xentop on its
> own account, not just to satisfy Keir's (sensible) requirement.

My further fear about domain runstates is that it adds an extra cost on
every VCPU schedule/deschedule, linear in number of vcpus. We want to keep
that path short, not add extra accounting crap to it.

 -- Keir

> Ian.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-11-25 22:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 11:26 [PATCH] xen: Implement domain runstates George Dunlap
2010-11-23 12:51 ` Keir Fraser
2010-11-23 14:23   ` George Dunlap
2010-11-23 15:00     ` Keir Fraser
2010-11-23 15:48       ` George Dunlap
2010-11-23 18:41         ` Pasi Kärkkäinen
2010-11-25 19:11         ` Ian Jackson
2010-11-25 22:10           ` Keir Fraser [this message]
2010-11-25 20:02         ` Bruce Edge
2010-11-25 22:24           ` Keir Fraser
2010-11-25 22:32             ` Bruce Edge
2010-11-26 11:52             ` George Dunlap

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=C9148F71.B223%keir@xen.org \
    --to=keir@xen.org \
    --cc=Ian.Jackson@eu.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 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.