bitkeeper revision 1.1159.1.310 (41828879uBRmYC81TaPfV6LGMJ1TYw)

Doc fixes.
This commit is contained in:
kaf24@freefall.cl.cam.ac.uk committed 2004-10-29 18:14:17 +00:00
1 parent 62ac41be63
commit 1950b07711
2 files changed
+23 -21

No files matched your search

+10 -9
View File
@@ -8,7 +8,7 @@ __ __ ____ ___
###############################
University of Cambridge Computer Laboratory
28 October 2004
29 October 2004
http://www.cl.cam.ac.uk/netos/xen/
http://www.cl.cam.ac.uk/netos/xen/
@@ -16,17 +16,18 @@ http://www.cl.cam.ac.uk/netos/xen/
About the Xen Virtual Machine Monitor
=====================================
"Xen" is a Virtual Machine Monitor (VMM) originally developed by the
Xen is a Virtual Machine Monitor (VMM) originally developed by the
Systems Research Group of the University of Cambridge Computer
Laboratory, as part of the UK-EPSRC funded XenoServers project.
Laboratory, as part of the UK-EPSRC funded XenoServers project.
Xen 2.0 offers excellent performance, hardware support and enterprise
grade features such as live migration. Linux 2.6, 2.4 and NetBSD 2.0
are already available for Xen, with more operating system ports on the
way.
The 2.0 release offers excellent performance, hardware support and
enterprise-grade features such as live migration. Linux 2.6, 2.4 and
NetBSD 2.0 are already available for Xen, with more operating system
ports on the way.
Xen is Free Open Source Software, released under the GNU GPL.
Xen is freely-distributable Open Source software, released under the
GNU GPL.
For full documentation, see the Xen User Manual in docs/user.pdf
For full documentation, see the Xen User Manual in docs/pdf/user.pdf
(after running make -C docs) or the Documentation page on the Xen
website.
+13 -12
View File
@@ -12,7 +12,7 @@ make this release: We have plans for a "universal buffer cache" that
enables otherwise unused system memory to be used by domains in a
read-only fashion.
Disk Scheduling
Disk scheduling
---------------
The current disk scheduler is rather simplistic (batch round robin),
and could be replaced by e.g. Cello if we have QoS isolation
@@ -27,7 +27,7 @@ assigned to a CPU when they are created (in a round robin fashion).
We'd like to see a user-space load-balancing daemon that can shift
domains between CPUs as their activity changes.
Multiprocessor Guest VMs
Multiprocessor guest VMs
------------------------
Xen currently only supports uniprocessor guest OSes. We have designed
the Xen interface with MP guests in mind, and plan to build an MP
@@ -40,7 +40,7 @@ still has the page in its TLB to ensure memory system integrity. One
other issue for supporting MP guests is that we'll need some sort of
CPU gang scheduler, which will require some research.
Cluster Management
Cluster management
------------------
There have been discussions regarding a unified cluster controller
for Xen deployments. This would leverage the existing features of
@@ -48,12 +48,13 @@ Xen to present a uniform control interface for managing a cluster
as a pool of resources, rather than a set of completely distinct
machines.
PAE Support on 32-bit x86
-------------------------
Xen can currently use up to 4GB of memory. It's possible for x86
machines to address more than that (64GB), but it requires using a
different page table format (3-level rather than 2-level) that we
currently don't support. Adding 3-level PAE support wouldn't be
difficult, but we'd also need to add support to all the guest
OSs. We do not plan to add this support ourselves but volunteers
are welcome!
64-bit x86
----------
Xen can currently use up to 4GB of memory. It's possible for 32-bit
x86 machines to address up to 64GB, but it requires using a different
page table format that would be rather tedious to support. Our
preferred approach is to virtualize 64-bit x86 (x86/64), as supported
by modern AMD and Intel processors. The large address space provided
by a 64-bit execution model greatly simplifies support for large-memory
configurations. Our implementation for x86/64 is in progress and should
feature in our next major release.
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.