From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Rushton Subject: Re: [RFC PATCH] page_alloc: use first half of higher order chunks when halving Date: Fri, 11 Apr 2014 13:20:26 -0700 Message-ID: <53484E8A.4020106@gmail.com> References: <5332F948.1020909@gmail.com> <20140326163609.GD21368@phenom.dumpdata.com> <533312C0.1050507@gmail.com> <20140326175606.GA24179@phenom.dumpdata.com> <5333518E.40203@gmail.com> <20140328170201.GB12659@phenom.dumpdata.com> <5335F25F.9050309@gmail.com> <20140331141500.GB3159@phenom.dumpdata.com> <533A31B7.8090608@gmail.com> <20140401104825.GA5342@localhost.localdomain> <20140401122223.GA62612@deinos.phlegethon.org> <533B5732.6050001@gmail.com> <533BDDF0020000780000489C@nat28.tlf.novell.com> <1396433179.8667.292.camel@kazak.uk.xensource.com> <533BFF7D02000078000049B8@nat28.tlf.novell.com> <1396434020.8667.300.camel@kazak.uk.xensource.com> <5345C7F2.5050005@gmail.com> <534652FD0200007800007732@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WYhw9-0007fl-Jh for xen-devel@lists.xenproject.org; Fri, 11 Apr 2014 20:20:33 +0000 Received: by mail-pb0-f54.google.com with SMTP id ma3so5853515pbc.27 for ; Fri, 11 Apr 2014 13:20:30 -0700 (PDT) In-Reply-To: <534652FD0200007800007732@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Keir Fraser , Ian Campbell , AndrewCooper , Tim Deegan , Matt Wilson , Matt Wilson , xen-devel@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org On 04/09/14 23:14, Jan Beulich wrote: >>>> On 10.04.14 at 00:21, wrote: >> On 04/02/14 03:20, Ian Campbell wrote: >>> Dom0 ballooning breaks any assumptions you might make about relying on >>> early allocations. >> I think you're missing the point. I'm not arguing that this change is a >> general purpose solution to guarantee that dom0 is contiguous. >> Fragmentation can exist even if dom0 asks for larger allocations like it >> should (which the balloon driver does I believe). What the change does >> do is solve a real problem in the current Linux PCI remapping >> implementation which happens during dom0 intialization. If the >> allocation strategy is arbitrary why not make the proposed hypervisor >> change to make existing Linux implementations behave better and in >> addition fix the problem in Linux so moving forward things are safe? > Apart from all other arguments speaking against this, did you > consider that altering the hypervisor behavior may adversely > affect some other Dom0-capable OS? Sure I've been considering the more intuitive dom0 implementation of allocating memory low to high and looking at things pragmatically. > > Problems in Linux should, as said before, get fixed in Linux. If > older versions are affected, stable backports should subsequently > be requested/done. > > Jan >