All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aron Griffis <aron@hp.com>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Insane contiguous physical memory requirements in blkbk/blktap
Date: Thu, 5 Oct 2006 11:38:39 -0400	[thread overview]
Message-ID: <20061005153838.GA25054@fc.hp.com> (raw)
In-Reply-To: <1160053870.6513.25.camel@sisko.scot.redhat.com>

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

  reply	other threads:[~2006-10-05 15:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 13:11 Insane contiguous physical memory requirements in blkbk/blktap Stephen C. Tweedie
2006-10-05 15:38 ` Aron Griffis [this message]
2006-10-05 15:47   ` Keir Fraser
2006-10-05 16:10     ` Stephen C. Tweedie
2006-10-05 16:19       ` Keir Fraser
2006-10-05 16:40         ` Stephen C. Tweedie
2006-10-05 16:43           ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061005153838.GA25054@fc.hp.com \
    --to=aron@hp.com \
    --cc=sct@redhat.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.