Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755618AbZKJCmD (ORCPT ); Mon, 9 Nov 2009 21:42:03 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755342AbZKJCmC (ORCPT ); Mon, 9 Nov 2009 21:42:02 -0500 Received: from ozlabs.org ([203.10.76.45]:59164 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752873AbZKJCmB (ORCPT ); Mon, 9 Nov 2009 21:42:01 -0500 From: Rusty Russell To: Adam Litke Subject: Re: virtio: Add memory statistics reporting to the balloon driver Date: Tue, 10 Nov 2009 13:12:02 +1030 User-Agent: KMail/1.12.2 (Linux/2.6.31-14-generic; KDE/4.3.2; i686; ; ) Cc: qemu-devel@nongnu.org, "Anthony Liguori" , Avi Kivity , virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org References: <1257782838.2835.5.camel@aglitke> <1257784326.2835.16.camel@aglitke> In-Reply-To: <1257784326.2835.16.camel@aglitke> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <200911101312.02650.rusty@rustcorp.com.au> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 645 Lines: 15 On Tue, 10 Nov 2009 03:02:06 am Adam Litke wrote: > A simpler approach is to collect memory statistics in the virtio > balloon driver and communicate them to the host via the device config space. There are two issues I see with this. First, there's an atomicity problem since you can't tell when the stats are consistent. Second, polling is ugly. A stats vq might solve this more cleanly? Rusty. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/