All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Williamson <maw48@cl.cam.ac.uk>
To: xen-devel@lists.sourceforge.net
Cc: Jerome Brown <jerome@concepts.net.nz>
Subject: Re: uClibc
Date: Wed, 22 Dec 2004 01:48:17 +0000	[thread overview]
Message-ID: <200412220148.17524.maw48@cl.cam.ac.uk> (raw)
In-Reply-To: <41C88D03.2090409@concepts.net.nz>

> How do the resources used differ?

I can't put exact numbers on it but using Python will certainly result in a 
larger memory footprint being necessary for domain 0.

Python's not an enormously fast language but that doesn't matter too much for 
control plane functionality (performance critical stuff is coded in C 
already).

> Is Xend currently in python?

The control tools and Xend are written in Python.

The migration / suspend daemon (xfrd) is also coded in C for performance 
reasons.

> Is there 
> a plan to change this? What has been the reasoning behind developing it
> in python?

The use of Python in Xend enables rapid development - Xend does _a lot_ of 
different tasks, so it's good to have as much high-level goodness on your 
side as possible.  I don't think we're likely to change language in the near 
future.

Compared to the amount of memory spent on other domains, Xend's footprint is 
arguably still likely to be pretty small, although obviously it depends 
somewhat on the application.

The lowlevel functions for interfacing to Xen are available in a separate C 
library so it's possible to hook arbitrary languages into Xen.  It's 
certainly possible for Xend to be rewritten in C but it would be a large job 
to provide equivalent functionality.

An alternative control daemon called "x2d2" is in the unstable tree (what 
about the testing tree?  not sure...) but this is intended for developer 
experimentation and is not a full-blown Xend replacement.

Cheers,
Mark

>
> > Input and cooperation is welcomed.
>
> I'd love to help. I like the idea of a 'self installing' dom0 that sets
> up another control domain, thereby abstracting all the running processes
> into unprivileged domains for security reasons. As part of this I will
> look to create a HowTo document that details how I acheive this :)
>
> Regards
>
> Jerome
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  parent reply	other threads:[~2004-12-22  1:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21 20:14 uClibc Jerome Brown
2004-12-21 20:36 ` uClibc Jacob Gorm Hansen
2004-12-21 20:52   ` uClibc Jerome Brown
2004-12-21 21:11     ` uClibc Jacob Gorm Hansen
2004-12-21 22:44       ` uClibc Kip Macy
2004-12-21 15:20         ` uClibc Jacob Gorm Hansen
2004-12-21 23:36         ` uClibc Jacob Gorm Hansen
2004-12-22  1:48     ` Mark Williamson [this message]
2015-12-19  9:18 uclibc Markus Volk
2015-12-19  9:34 ` uclibc Khem Raj

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=200412220148.17524.maw48@cl.cam.ac.uk \
    --to=maw48@cl.cam.ac.uk \
    --cc=jerome@concepts.net.nz \
    --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 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.