From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757118AbYG0Gn5 (ORCPT ); Sun, 27 Jul 2008 02:43:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758751AbYG0Gns (ORCPT ); Sun, 27 Jul 2008 02:43:48 -0400 Received: from ozlabs.org ([203.10.76.45]:47634 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758740AbYG0Gnq (ORCPT ); Sun, 27 Jul 2008 02:43:46 -0400 From: Rusty Russell To: virtualization@lists.linux-foundation.org Subject: Re: How to get a sense of VM pressure Date: Sun, 27 Jul 2008 16:43:31 +1000 User-Agent: KMail/1.9.9 Cc: Jeremy Fitzhardinge , Linux Kernel Mailing List , Virtualization Mailing List , Rik van Riel , Andrew Morton , Linux Memory Management List References: <488A1398.7020004@goop.org> In-Reply-To: <488A1398.7020004@goop.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807271643.32338.rusty@rustcorp.com.au> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Saturday 26 July 2008 03:55:36 Jeremy Fitzhardinge wrote: > So I guess what I need is some measurement of "memory use" which is > perhaps akin to a system-wide RSS; a measure of the number of pages > being actively used, that if non-resident would cause a large amount of > paging. If you shrink the domain down to that number of pages + some > padding (x%?), then the system will run happily in a stable state. If > that number increases, then the system will need new memory soon, to > stop it from thrashing. And if that number goes way below the domain's > actual memory allocation, then it has "too much" memory. Like everyone, I've thought about this. The shrinker callbacks seem like a candidate here; have you played with them at all? Some dynamic tension between the shrinker callback and slow feed of pages to the balloon seems like it should work... Rusty.