All of lore.kernel.org
 help / color / mirror / Atom feed
* physmap deallocation on balloon?
@ 2008-04-09  0:39 Michael R. Hines
  2008-04-09  0:52 ` weiming
  0 siblings, 1 reply; 2+ messages in thread
From: Michael R. Hines @ 2008-04-09  0:39 UTC (permalink / raw)
  To: xen-devel


[-- Attachment #1.1: Type: text/plain, Size: 643 bytes --]

Greetings,

Currently, as I understand PV memory allocation,
the Guest's pfn -> mfn physmap will get populated
on-demand as the guest uses more an more of its
memory reservation.

Is it possible to also make this go in the reverse direction?

For example: let's say we have a guest that is mostly idle
and has a great deal of free memory and we decide to balloon
down the domain. In addition to decreasing the domain's
reservation, is it also possible to remove the physmap entries
in an on-demand fashion as memory is freed up?

-- 
/*
Michael R. Hines
http://www.cs.binghamton.edu/~mhines/
Live long and prosper...
*/


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: physmap deallocation on balloon?
  2008-04-09  0:39 physmap deallocation on balloon? Michael R. Hines
@ 2008-04-09  0:52 ` weiming
  0 siblings, 0 replies; 2+ messages in thread
From: weiming @ 2008-04-09  0:52 UTC (permalink / raw)
  To: mhines; +Cc: xen-devel


[-- Attachment #1.1: Type: text/plain, Size: 1395 bytes --]

Hi,

I guess it's possible but the effect might be not obvious. When you shrink
the reservation by one page (4K), you just save one entry.

And currently, ballooning works as a kernel module which, from kernel's
perspective, just simple allocates / frees pages. It makes the code simple
and easier. Resizing the mapping table complicates it. And you'd better keep
the table contiguous. It's nasty.

Just my 2 cents. Correct me if I'm wrong.

Thanks,
Weiming

On Tue, Apr 8, 2008 at 8:39 PM, Michael R. Hines <mhines@cs.binghamton.edu>
wrote:

> Greetings,
>
> Currently, as I understand PV memory allocation,
> the Guest's pfn -> mfn physmap will get populated
> on-demand as the guest uses more an more of its
> memory reservation.
>
> Is it possible to also make this go in the reverse direction?
>
> For example: let's say we have a guest that is mostly idle
> and has a great deal of free memory and we decide to balloon
> down the domain. In addition to decreasing the domain's
> reservation, is it also possible to remove the physmap entries
> in an on-demand fashion as memory is freed up?
>
> --
> /*
> Michael R. Hines
> http://www.cs.binghamton.edu/~mhines/<http://www.cs.binghamton.edu/%7Emhines/>
> Live long and prosper...
> */
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>

[-- Attachment #1.2: Type: text/html, Size: 1933 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2008-04-09  0:52 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-04-09  0:39 physmap deallocation on balloon? Michael R. Hines
2008-04-09  0:52 ` weiming

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.