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

RE: [Xen-ia64-devel]Found the lost memory.


  • To: "Alex Williamson" <alex.williamson@xxxxxx>
  • From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • Date: Tue, 28 Feb 2006 14:52:45 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 28 Feb 2006 06:53:26 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcY8GnU2Z9YH0Z5PQPORiecHxSvoPwAGH5GA
  • Thread-topic: [Xen-ia64-devel]Found the lost memory.


Thanks,
-Anthony 

>From: Alex Williamson 
>Sent: 2006年2月28日 11:50
>   Anything that flags the issue as a problem is an improvement IMHO.
>Ideally we could do something that will automatically work when
>max_pages is equal to the top of physical memory (hopefully that will
>cover the efi.c hack as well).  Perhaps an ia64_init_domheap_pages()
>wrapper that does the appropriate top of memory/max_pages check so we
>can avoid changing xen common code.  When we have our ia64 specific
>memory issues worked out, this wrapper could degenerate and go away.
>Would something like that work?  Thanks,
>

This patch can work around virtual memmap/discontig memory issues, but memory 
gain may not be realized.

Signed-off-by: Anthony Xu <anthony.xu@xxxxxxxxx>

Thanks,
Anthony

Attachment: fix_memory_reclaim.patch
Description: fix_memory_reclaim.patch

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