public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Rik van Riel <riel@redhat.com>
Cc: Mark Williamson <maw48@cl.cam.ac.uk>,
	xen-devel@lists.sourceforge.net,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] Re: [XEN] using shmfs for swapspace
Date: Thu, 6 Jan 2005 11:38:27 +0000	[thread overview]
Message-ID: <20050106113827.GM6440@lkcl.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0501040902400.25392@chimarrao.boston.redhat.com>

On Tue, Jan 04, 2005 at 09:05:13AM -0500, Rik van Riel wrote:
> On Tue, 4 Jan 2005, Mark Williamson wrote:
> 
> >>for doing opportunistic page recycling ("I dont need this page but when
> >>I ask for it back please tell me if you trashed the content")
> >
> >We've talked about doing this but AFAIK nobody has gotten round to it 
> >yet because there hasn't been a pressing need (IIRC, it was on the todo 
> >list when Xen 1.0 came out).
> >
> >IMHO, it doesn't look terribly difficult but would require (hopefully 
> >small) modifications to the architecture independent code, plus a little 
> >bit of support code in Xen.
> 
> The architecture independant changes are fine, since
> they're also useful for S390(x), PPC64 and UML...
> 
> >I'd quite like to look at this one fine day but I suspect there are more 
> >useful things I should do first...
> 
> I wonder if the same effect could be achieved by just
> measuring the VM pressure inside the guests and
> ballooning the guests as required, letting them grow
> and shrink with their workloads.
 
 mem = 64M-128M
 target = 64M

 "if needed, grow me to 128mb but if not, whittle down to 64".

 mem=64M-128
 target=128M

 "if you absolutely have to, steal some of my memory, but don't nick
 any more than 64M".

 i'm probably going to have to "manually" implement something like this.

 l.


  reply	other threads:[~2005-01-06 11:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-02 16:26 [XEN] using shmfs for swapspace Luke Kenneth Casson Leighton
2005-01-03 18:31 ` Joseph Fannin
2005-01-03 20:53   ` Luke Kenneth Casson Leighton
2005-01-03 21:06     ` Alan Cox
2005-01-04  3:04       ` [Xen-devel] " Mark Williamson
2005-01-04 14:05         ` Rik van Riel
2005-01-06 11:38           ` Luke Kenneth Casson Leighton [this message]
2005-01-05  0:11         ` Arnd Bergmann
2005-01-21 21:37           ` Rik van Riel
2005-01-26 20:56             ` Mark Williamson
2005-01-27 10:33               ` Nuutti Kotivuori
2005-01-03 21:07     ` Adam Heath
2005-01-04  9:30       ` Luke Kenneth Casson Leighton
2005-01-04 14:06         ` Rik van Riel

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=20050106113827.GM6440@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maw48@cl.cam.ac.uk \
    --cc=riel@redhat.com \
    --cc=xen-devel@lists.sourceforge.net \
    /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