On Sun, 2009-07-19 at 04:25 +0800, Thomas Goirand wrote:
>
> In both cases, the goal is to avoid forking yet another process, by
> calling "xm list", "xm stop" or "xm start" for example, by simply
> including some python code and calling the main.
FWIW I'd be surprised if the upstream Xen developers would consider this
to be a stable/exported interface.
Is performance of "xm start" and "xm stop" really bounded by the time it
takes to fork the python process for xm? Seems unlikely to me. Similarly
if time to fork "xm list" is an issue then perhaps you are polling far
to frequently?
Ian.
--
Ian Campbell
Current Noise: Electric Wizard - Priestess Of Mars
toilet toup'ee, n.:
Any shag carpet that causes the lid to become top-heavy, thus
creating endless annoyance to male users.
-- Rich Hall, "Sniglets"
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
