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

RE: [Xen-ia64-devel] Virtual mem map


  • To: "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Mon, 9 Jan 2006 23:36:07 +0800
  • Delivery-date: Mon, 09 Jan 2006 15:42:38 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcYVMfcG0Rf2tI6TSBuVAZCzN14n9QAAGjmw
  • Thread-topic: [Xen-ia64-devel] Virtual mem map

>From: Tristan Gingold [mailto:Tristan.Gingold@xxxxxxxx]
>Sent: 2006年1月10日 0:35
>
>[...]
>> > >I think this structure is simple enough to be fast.
>> > >
>> > >For memory usage:
>> > >* Each entry of the first array describes 1GB of memory.  An entry is 32
>> > > bits. 16KB for the first array can describe 2**12 * 2**30 = 2**42 B of
>> > > memory. (Dan's machine physical memory is bellow 2**40).
>> > >* I think 1GB of granule is good enough, unless you have a machine with
>> > > very small DIMM.  In this case, we can use 512MB or 256MB instead of
>> > > 1GB. * 1GB is 2**16 to 2**18 pages.  Thus, the offset may be 18 bits
>> > > and the length 14 bits (to be multiplied by 4).
>> > >As a conclusion, the memory footprint is *very* small, maybe too small ?
>> > >
>> > >memmap related macros must be rewritten.
>> > >
>> > >Tristan.
>Hugh,  I forgot we need also reverse mapping.  I now understand the root of
>virtual mem map!
>
>Tristan.

Yes, exactly.

Thanks,
Kevin

_______________________________________________
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®.