From: Allen Short <washort@divmod.com>
To: xen-devel@lists.xensource.com
Subject: xend leaks/bugs/etc
Date: Sat, 16 Apr 2005 13:08:38 -0500 [thread overview]
Message-ID: <1113674918.17788.9.camel@multivac> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 751 bytes --]
Hi. I'm a Twisted developer interested in improving xend. First, I'm
going to ensure that it runs on Twisted 2.0. I'd also like to see if I
can reproduce the memory leaks I've seen reported here, and find out
what can be done about them. Eventually I'd like to refactor most of
xend to use Twisted's service architecture, which handles things like
startup and shutdown in a more modular fashion. (I'm working on a
project that could benefit from tighter integration with xend, but the
current codebase is not very friendly to that.) Is there a list of
existing problems with xend that I could refer to? I attempted to
reproduce the "xm list" memory leak, but was not able to do so. (I am
using Python 2.4.1 and yesterday's xeno-unstable.)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- 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
next reply other threads:[~2005-04-16 18:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 18:08 Allen Short [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-17 15:42 xend leaks/bugs/etc Ian Pratt
2005-04-18 6:00 ` Allen Short
2005-04-18 14:32 ` Harry Butterworth
2005-04-18 15:15 ` Anthony Liguori
2005-04-18 15:27 ` Hollis Blanchard
2005-04-18 15:45 ` Anthony Liguori
2005-04-18 16:16 ` Hollis Blanchard
2005-04-18 16:49 ` Harry Butterworth
2005-04-18 18:01 ` Anthony Liguori
2005-04-18 17:53 ` Hollis Blanchard
2005-04-20 7:10 ` Jacob Gorm Hansen
2005-04-20 14:16 ` Anthony Liguori
2005-04-21 22:58 ` Jacob Gorm Hansen
2005-04-22 0:21 ` Anthony Liguori
2005-04-18 15:58 ` Harry Butterworth
2005-04-18 21:33 ` Mike D. Day
2005-04-18 23:12 Ian Pratt
2005-04-20 7:54 ` Jacob Gorm Hansen
2005-04-20 14:34 ` Hollis Blanchard
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=1113674918.17788.9.camel@multivac \
--to=washort@divmod.com \
--cc=xen-devel@lists.xensource.com \
/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.