This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] disk throttling

To: Jacob Gorm Hansen <jacob@xxxxxxxx>
Subject: Re: [Xen-devel] disk throttling
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sat, 13 Nov 2004 01:21:53 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx, mark.williamson@xxxxxxxxxxxx
Delivery-date: Sat, 13 Nov 2004 01:51:56 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Fri, 12 Nov 2004 15:17:09 +0100." <4194C5E5.70404@xxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> I know you guys focus primarily on server-class machines, but I am 
> dreaming of running Xen on a 1000+ node cluster we have here, and with 
> the current mem usage of dom0 (according to postings on this list it has 
> a hard time coping on 32megs or less), this would waste at least 32 
> gigabytes of mem, just for dom0s.

Yes, but it's still the same fraction of total memory. If you can
afford a 1000-node cluster with terabytes of RAM then 32GB is utterly

 -- Keir

This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>