From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Design question for PV superpage support
Date: Tue, 03 Mar 2009 09:28:39 -0800
Message-ID: <49AD68C7.5000305@goop.org>
References: <a6ec1b4a-f245-4b42-9c63-5b16877af761@default>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <a6ec1b4a-f245-4b42-9c63-5b16877af761@default>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Dave McCracken <dcm@mccr.org>, Mick.Jordan@sun.com, Xen Developers List <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

Dan Magenheimer wrote:
> BTW, thinking ahead to ballooning with 2MB pages, are we prepared
> to assume that a relinquished 2MB page can't be fragmented?
> While this may be appealing for systems where nearly all
> guests are using 2MB pages, systems where the 2MB guest is
> an odd duck might suffer substantially by making that
> assumption.
>   

Well, I still think that 4k pages are a ludicrously tiny unit of memory 
for Xen to be dealing with, and it shouldn't bother to get out of bed 
for less than 2M.  If we treat 4k pages as the special case then keeping 
the Xen heap unfragmented at the 2M level should be fairly easy, no?

    J