From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aron Griffis Subject: Re: Insane contiguous physical memory requirements in blkbk/blktap Date: Thu, 5 Oct 2006 11:38:39 -0400 Message-ID: <20061005153838.GA25054@fc.hp.com> References: <1160053870.6513.25.camel@sisko.scot.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: <1160053870.6513.25.camel@sisko.scot.redhat.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Stephen C. Tweedie" Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Stephen C. Tweedie wrote: [Thu Oct 05 2006, 09:11:10AM EDT] > blkbk and blktap do not load reliably as modules. also netbk > As soon as you hit a > boot where a fs needs to be fscked, memory gets fragmented, and the > order-10 (yes, *TEN*) kmalloc in balloon_alloc_empty_page_range() fails. On ia64, we don't need an fsck for the failure to occur. The modules almost always fail to load. This is really screwing up xen/ia64 on Fedora right now. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=202971 > But is there any need at all for these pages to be contiguous? I've been looking at the exact same question, but don't know the answer. If you come up with a patch before I do, I'd be thrilled to test it. Aron