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] Insane contiguous physical memory requirements in blkbk/

To: "Stephen C. Tweedie" <sct@xxxxxxxxxx>
Subject: Re: [Xen-devel] Insane contiguous physical memory requirements in blkbk/blktap
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 05 Oct 2006 17:43:37 +0100
Cc: Aron Griffis <aron@xxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 05 Oct 2006 09:45:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1160066440.6513.45.camel@xxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbonWd3pg1zeFSQEduhdwAX8io7RQ==
Thread-topic: [Xen-devel] Insane contiguous physical memory requirements in blkbk/blktap
User-agent: Microsoft-Entourage/11.2.5.060620
On 5/10/06 17:40, "Stephen C. Tweedie" <sct@xxxxxxxxxx> wrote:

> OK, I was looking at blkback in this case.  Indexing is easy, we already
> have page->index for that purpose, and I don't think there's anything
> else using that for these pages once they are detached from the main VM.
> 
> Is there any reason we're not using memory in the vmalloc area for these
> things?  That memory is *supposed* to be allocated out for virtual use
> on demand.

In most cases we want the 'struct page' as well as the virtual address
space. For example, to stuff into skbuff fragment lists or block-device
scatter-gather lists. Kmalloc() gets us both those things -- it's just the
underlying mapped RAM we don't want. ;-)

 -- Keir



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