[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] xenballoond.init: remove 4 from default runlevel

> From: Olaf Hering [mailto:olaf@xxxxxxxxx]
> Subject: [Xen-devel] [PATCH] xenballoond.init: remove 4 from default runlevel
> # HG changeset patch
> # User Olaf Hering <olaf@xxxxxxxxx>
> # Date 1349458470 -7200
> # Node ID 65ab6762cd37d0f43ff031e00637d5a88514aadb
> # Parent  964fd4a693f940b5ae31d6d9021e0c89afaee703
> xenballoond.init: remove 4 from default runlevel
> Remove 4 from default runlevel in xenballoond.init.

Hi Olaf --

No objection to the patch, but I was wondering...

Are you using xenballoond for something?  (e.g. your page-sharing
testing or a product implementation)

I stopped encouraging the use of userland selfballooning (which
is what xenballoond implements) years ago, when I saw
the impact of very sudden large workload increases...
thrashing can occur.  This observation is what led to
tmem persistent pools and to selfballooning built into
the Linux kernel.

If you were just scanning Xen system services and ran across
this issue, no problem.  But since it is somewhat related
to your page-sharing/host-swapping work, I thought I'd check.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.