| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] Re: [XEN] using shmfs for swapspace
I could be wrong, but I think the significance was that on the s390,
the kernel (periodically) gave pages back to the hypervisor, and
requested memory back via the balloon driver only when needed.
I don't know how the balloon driver is implimented here, but in the
past I had wondered if it would be possible for the kernel to try and
increase memory via the balloon driver before calling the oom killer.
It seems to me like giving memory to the hypervisor when it wasn't
needed could be handled in userspace by monitoring /proc/meminfo, but
I think requesting memory would have to be within the kernel in order
to be able to make the attempt when there is no memory free but before
the oom killer kicks in. I was considering trying to impliment a
daemon like that in userspace, but I don't think it would be reliable
and would depend a lot on guesswork to try and pull in memory before
it was needed.
On Fri, 21 Jan 2005 16:37:09 -0500 (EST), Rik van Riel <riel@xxxxxxxxxx> wrote:
> On Wed, 5 Jan 2005, Arnd Bergmann wrote:
> > - Ballooning:
>
> Xen already has this. I wonder if it makes sense to
> consolidate the various balloon approaches into a single
> driver, and keep the amount of ballooned memory into
> account when reporting statistics in /proc/meminfo.
--
Puer Misellus Triste
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
|
|
| |
|
Home