WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] RE: Tmem vs order>0 allocation, workaround RFC

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Subject: Re: [Xen-devel] RE: Tmem vs order>0 allocation, workaround RFC
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Tue, 16 Feb 2010 13:20:50 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Andrew@xxxxxxxxxxxxxxxxxxxx, Grzegorz Milos <gm281@xxxxxxxxx>, George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, kurt.hackel@xxxxxxxxxx, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>, Deegan <Tim.Deegan@xxxxxxxxxxxxx>, Patrick Colp <pjcolp@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Tim@xxxxxxxxxxxxxxxxxxxx, Peace <Andrew.Peace@xxxxxxxxxxxxx>
Delivery-date: Tue, 16 Feb 2010 10:43:24 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <d2556e50-476d-487d-8fa8-aae67f63396c@default>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <2af13319-6b44-44e2-ab62-a0615208cf64@default> <C79F1B58.A196%keir.fraser@xxxxxxxxxxxxx> <78c49794-4454-4c3b-80a6-72efcbc73fb3@default> <78c49794-4454-4c3b-80a6-72efcbc73fb3@default> <057c0f45-9c97-4b8a-8efa-1726fd951e19@default4B7A6363020000780002F93C@vpn.id2.novell.com> <d2556e50-476d-487d-8fa8-aae67f63396c@default>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05)
On Tue, Feb 16, 2010 at 07:05:48AM -0800, Dan Magenheimer wrote:
> Hi Jan --
> 
> Thanks for thinking about this.
> 
> > may not work well: When you have 1Tb, you'd reserve 8G, making Dom0
> > single-page-below-4G-allocations impossible (unless dom0_mem= was
> > used) if I read the logic correctly.
> 
> Good point.  But tmem doesn't work very well at all if dom0_mem
> isn't set as dom0 is hogging all the spare memory in the system
> so only fallow memory reclaimed from selfballooning domains
> can be used by tmem.
> 
> Under what circumstances does dom0 require single-page-below-4G
> allocations?  Is it only for bounce buffers for PCI passthrough
> of old devices with 32-bit addressing limitations?  Or am I
> missing a much more common case?  (I think it's important to

The software IO TLB is initialized unconditionally if no IOMMUs are found.
This is a 64MB + 32Kb chunk of memory that is exchanged with Xen to make sure
it is under the 32-bit mark.

> enumerate and understand -- and document -- all special needs
> of memory pages as Xen has been fairly careless/lucky with
> fragmentation so far, but with all the memory optimization
> technologies in 4.0, we need to root out all the cases.)
> 
> Thanks,
> Dan
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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