| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] Modular Xen
Makes a lot of sense IMHO.
It would also provide for better opportunity in extending Xen - some of
the features can really "get in your way" when you're trying to add new
features. This, for features you don't really need (did someone say
NUMA?).
Suppose I would be able to easily take out redundant stuff (without
having to go into the code and comment out a zillion lines of code), I
would be able to more easily develop initial implementations of new
features.
Later, I would put everything back in and make sure it all works
together. But that's the final stage of such a project, shouldn't be
mandatory at the pilot stages...
My 2c
Ilan Horn
Chief Software Architect, Neocleus Inc.
-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of David Pilger
Sent: Monday, January 15, 2007 7:30 PM
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Modular Xen
It seems to me that Xen is full of stuff that aren't beneficial for
everybody, this includes NUMA, ACM and other stuff that certain
companies try to introduce... In a better world, the Xen binary would
have been more sleek and fast, and those extra features should be loaded
via stating a Module boot line in Grub. This way, testing would be easy
and it's more elegant than using a compilation flag.
Are there any thoughts to make Xen more modular in this manner?
It can be a real improvement for all of us freelancers that experiment
with this hot subject :)
Your thoughts?
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home