public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Chris Wright <chrisw@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: KVM call agenda for Apr 27
Date: Mon, 26 Apr 2010 17:36:52 -0500	[thread overview]
Message-ID: <4BD61584.9080208@codemonkey.ws> (raw)
In-Reply-To: <20100426221258.GH15278@x200.localdomain>

On 04/26/2010 05:12 PM, Chris Wright wrote:
> * Anthony Liguori (anthony@codemonkey.ws) wrote:
>    
>> On 04/26/2010 12:26 PM, Chris Wright wrote:
>>      
>>> Please send in any agenda items you are interested in covering.
>>>
>>> While I don't expect it to be the case this week, if we have a
>>> lack of agenda items I'll cancel the week's call.
>>>        
>> - qemu management interface (and libvirt)
>> - stable tree policy (push vs. pull and call for stable volunteers)
>>      
> block plug in (follow-on from qmp block watermark)
>    

A few comments:

1) The problem was not block watermark itself but generating a 
notification on the watermark threshold.  It's a heuristic and should be 
implemented based on polling block stats.  Otherwise, we'll be adding 
tons of events to qemu that we'll struggle to maintain.

2) A block plugin doesn't solve the problem if it's just at the 
BlockDriverState level because it can't interact with qcow2.

3) For general block plugins, it's probably better to tackle userspace 
block devices.  We have CUSE and FUSE already, a BUSE is a logical 
conclusion.

Regards,

Anthony Liguori


  reply	other threads:[~2010-04-26 22:36 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 [this message]
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
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=4BD61584.9080208@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=chrisw@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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