From: Rusty Russell <rusty@rustcorp.com.au>
To: virtualization@lists.linux-foundation.org
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Rik van Riel <riel@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: How to get a sense of VM pressure
Date: Sun, 27 Jul 2008 16:43:31 +1000 [thread overview]
Message-ID: <200807271643.32338.rusty@rustcorp.com.au> (raw)
In-Reply-To: <488A1398.7020004@goop.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.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-07-27 6:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 17:55 Jeremy Fitzhardinge
2008-07-26 4:25 ` Nick Piggin
2008-07-27 3:14 ` Dave Hansen
2008-07-28 8:10 ` Jeremy Fitzhardinge
2008-07-27 6:43 ` Rusty Russell [this message]
2008-07-28 7:36 ` Peter Zijlstra
2008-07-28 8:12 ` Jeremy Fitzhardinge
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=200807271643.32338.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=virtualization@lists.osdl.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