From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "dan.magenheimer@oracle.com" <dan.magenheimer@oracle.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ky Srinivasan <KSrinivasan@novell.com>,
Jan Beulich <jbeulich@novell.com>, KurtGarloff <garloff@suse.de>
Subject: Re: [PATCH] linux/balloon: don't allow ballooningdowna domain below a reasonable limit
Date: Fri, 2 May 2008 00:03:10 +0100 [thread overview]
Message-ID: <20080502000310.361b9c99@core> (raw)
In-Reply-To: <C43FF23D.18160%keir.fraser@eu.citrix.com>
> It might be the case though that, in practice, vm_committed_space is a
> reasonable predictor for working set for some common types of workload. Many
> applications probably keep their heaps fairly warm and hence in main memory.
I am dubious. What vm_committed_space does allow you to do however if you
watch it in Xen is to actually ensure you never balloon out a virtual
machine to the point you make it start killing stuff off.
There are better ways to measure memory pressure - sizes of the various
active and inactive lists etc. OLPC has code for this and a proposed
memory pressure notifier feature that they use to allow user space apps
to cleanup.
next prev parent reply other threads:[~2008-05-01 23:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 15:07 [PATCH] linux/balloon: don't allow ballooning down a domain below a reasonable limit Jan Beulich
2008-04-05 21:39 ` Keir Fraser
2008-04-07 7:10 ` [PATCH] linux/balloon: don't allow ballooningdown " Jan Beulich
2008-04-29 18:35 ` Dan Magenheimer
2008-04-30 6:29 ` [PATCH] linux/balloon: don't allow ballooningdowna " Jan Beulich
2008-04-30 16:04 ` Dan Magenheimer
2008-04-30 23:49 ` Dan Magenheimer
2008-05-01 7:01 ` Keir Fraser
2008-05-01 14:44 ` Dan Magenheimer
2008-05-01 16:36 ` Alan Cox
2008-05-01 16:56 ` Keir Fraser
2008-05-01 20:05 ` Alan Cox
2008-05-01 16:59 ` Dan Magenheimer
2008-05-01 21:18 ` Keir Fraser
2008-05-01 23:03 ` Alan Cox [this message]
2008-05-01 23:27 ` Dan Magenheimer
2008-05-02 7:05 ` Keir Fraser
2008-05-03 13:53 ` Dan Magenheimer
2008-05-03 14:11 ` Keir Fraser
2008-05-03 19:27 ` Dan Magenheimer
2008-05-03 17:32 ` Mark Williamson
2008-05-03 19:43 ` Dan Magenheimer
2008-05-12 22:19 ` [PATCH] linux/balloon: don't allowballooningdowna " Ian Pratt
2008-05-12 23:34 ` Dan Magenheimer
2008-05-13 10:35 ` Markus Hochholdinger
-- strict thread matches above, loose matches on Subject: below --
2008-05-02 19:30 [PATCH] linux/balloon:don't allow ballooningdowna " Jan Beulich
2008-05-02 22:22 ` Dan Magenheimer
2008-05-03 13:24 ` Goswin von Brederlow
2008-05-09 20:38 ` Dan Magenheimer
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=20080502000310.361b9c99@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=KSrinivasan@novell.com \
--cc=dan.magenheimer@oracle.com \
--cc=garloff@suse.de \
--cc=jbeulich@novell.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.