public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: KVM call agenda for Apr 27
Date: Tue, 27 Apr 2010 08:21:20 -0500	[thread overview]
Message-ID: <4BD6E4D0.1030905@codemonkey.ws> (raw)
In-Reply-To: <4BD6E41E.7070106@redhat.com>

On 04/27/2010 08:18 AM, Kevin Wolf wrote:
>
> The watermark is not some complex computed value, but actually the
> statistic itself. We can get rid of handling a threshold in qemu by just
> signalling "something has changed with this stat".
>
> I'm really not arguing that qemu should do anything complex or even
> define policy. It's just about avoiding polling all the time when
> nothing has changed and polling too late when things are changing quickly.
>
>    
>> Polling is really the right solution.  It gives the management tool
>> ultimate flexibility in tweaking the heuristics as they see fit.
>>      
> Isn't providing this flexibility completely orthogonal to polling vs.
> event-based?
>    

Except then we need to offer a generic statistics mechanism which seems 
like it's going to add a fair bit of complexity.  So far, the only 
argument for it seems to be a misplaced notion that "polling is evil".

Regards,

Anthony Liguori

> Kevin
>    


  reply	other threads:[~2010-04-27 13:21 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 17:26 KVM call agenda for Apr 27 Chris Wright
2010-04-26 17:51 ` Anthony Liguori
2010-04-26 22:12   ` Chris Wright
2010-04-26 22:36     ` Anthony Liguori
2010-04-27  8:14       ` Avi Kivity
2010-04-27  8:48         ` Dor Laor
2010-04-27  8:56           ` Avi Kivity
2010-04-27  9:08             ` Dor Laor
2010-04-27  9:22               ` Avi Kivity
2010-04-27  9:32                 ` Dor Laor
2010-04-27  9:41                   ` Kevin Wolf
2010-04-27 13:15                     ` Anthony Liguori
2010-04-27  9:16             ` Kevin Wolf
2010-04-27  9:28               ` Avi Kivity
2010-04-27 13:03         ` Anthony Liguori
2010-04-27 13:08           ` Avi Kivity
2010-04-27 13:11           ` Daniel P. Berrange
2010-04-27 13:15             ` Gleb Natapov
2010-04-27 13:38               ` Daniel P. Berrange
2010-04-27 14:10                 ` Gleb Natapov
2010-04-27  8:53       ` [Qemu-devel] " Kevin Wolf
2010-04-27 13:10         ` Anthony Liguori
2010-04-27 13:18           ` Kevin Wolf
2010-04-27 13:21             ` Anthony Liguori [this message]
2010-04-27 13:42               ` Kevin Wolf
2010-04-27 13:48                 ` Anthony Liguori
2010-04-27 13:58                   ` Kevin Wolf
2010-04-27 14:01                     ` Anthony Liguori
2010-04-27 11:11       ` Gleb Natapov
2010-04-27 13:00         ` Anthony Liguori
2010-04-27 13:05           ` Gleb Natapov
2010-04-27 13:19             ` Anthony Liguori
2010-04-27 13:29               ` Gleb Natapov
2010-04-27  1:15   ` [Qemu-devel] " Luiz Capitulino
2010-04-27  3:39     ` Aurelien Jarno

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=4BD6E4D0.1030905@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=chrisw@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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