[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-ia64-devel] [PATCH][RFC] allow conflicted rid allocation for >64 domain


  • To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • From: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxxxxxxx>
  • Date: Tue, 29 May 2007 13:43:40 +0200
  • Delivery-date: Tue, 29 May 2007 04:41:43 -0700
  • Domainkey-signature: s=s768; d=fujitsu-siemens.com; c=nofws; q=dns; b=I+RFmTAtserW1shK3eBUCk8aedbbEEFRy7vVrhgBjsuT+i01rzmpgz9izjSxy8upp4G3j0INats8zsxsanJmxgVyqEh/rGJGmjC0S5hG5S/4G+xYM4hbAZ8OFybhGexr;
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>

Am Samstag, 26. Mai 2007 schrieb Tristan Gingold:
> On Mon, May 14, 2007 at 04:55:46PM +0900, Isaku Yamahata wrote:
> > It seems that we're approaching 64 domain limit.
> > Here's the experimental patch which removes it.
> > 
> > I don't think that just reducing rid bits given to guest OS is 
> > enough because presumably we need domains more than 128, 256 or
> > 512 ... eventually.
> > So my approach is to allow rid regions to conflict.
> > I haven't test it with >64 domains because my environment
> > doesn't have enough memory to boot so many domains.
> Late comment: you could create mini-os domain, they don't need a lot of
> memory!
When commenting out the call of 
init_netfront(&start_info);
in kernel.c, mini-os runs with only 2 MB of memory.

Dietmar.

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.