From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: KVM call agenda for Apr 27 Date: Mon, 26 Apr 2010 17:36:52 -0500 Message-ID: <4BD61584.9080208@codemonkey.ws> References: <20100426172634.GC15278@x200.localdomain> <4BD5D28C.7080700@codemonkey.ws> <20100426221258.GH15278@x200.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org To: Chris Wright Return-path: Received: from mail-gx0-f217.google.com ([209.85.217.217]:40075 "EHLO mail-gx0-f217.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752355Ab0DZWg5 (ORCPT ); Mon, 26 Apr 2010 18:36:57 -0400 Received: by gxk9 with SMTP id 9so898138gxk.8 for ; Mon, 26 Apr 2010 15:36:56 -0700 (PDT) In-Reply-To: <20100426221258.GH15278@x200.localdomain> Sender: kvm-owner@vger.kernel.org List-ID: 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