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] One question on alloc_bitmap

To: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, Daniel Magenheimer <dan.magenheimer@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Wang, Shane" <shane.wang@xxxxxxxxx>
Subject: Re: [Xen-devel] One question on alloc_bitmap
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Mon, 22 Sep 2008 08:03:05 +0100
Cc:
Delivery-date: Mon, 22 Sep 2008 00:03:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <E2263E4A5B2284449EEBD0AAB751098401ABCF3892@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AckaYm6X9On318q8Slued9v7025o9ACEoo0QAAMScRE=
Thread-topic: [Xen-devel] One question on alloc_bitmap
User-agent: Microsoft-Entourage/11.4.0.080122
Um, I was suggesting we *don't* use an explicit radix tree in this case (I
assume Dan has a diffeent scenario where he actually requires an explicit
radix tree structure). For alloc_bitmap[] we can stitch together a linear
virtual address space using page tables, just as we do for frame_table[].

 -- Keir

On 22/9/08 06:35, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote:

> Sure, can you please share the patch to avoid duplicate patch?
> 
> Thanks
> Yunhong Jiang
> 
> Daniel Magenheimer <mailto:dan.magenheimer@xxxxxxxxxx> wrote:
>> FYI, I'm working on a patch that requires radix trees and
>> have borrowed a bunch of code from Linux for it.  I had
>> to make a few changes to generalize the code (e.g.
>> callouts for node alloc/free); if it would be useful,
>> please let me know and I will post it.
>> 
>>> -----Original Message-----
>>> From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx]
>>> Sent: Friday, September 19, 2008 3:32 AM
>>> To: Jiang, Yunhong; xen-devel@xxxxxxxxxxxxxxxxxxx; Wang, Shane
>>> Subject: Re: [Xen-devel] One question on alloc_bitmap
>>> 
>>> 
>>> On 19/9/08 10:17, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote:
>>> 
>>>>>> Any idea on it?
>>>>> 
>>>>> Yes, it could be sparsely allocated in future. No reason why not.
>>>> 
>>>> Thanks for your clarification. We ask this because we are considering
>>>> memory online.
>>> 
>>> I would suggest we allocate a virtual address range for the
>>> bitmap and then
>>> demand-populate mappings in that area. Just as we do for the frame_table.
>>> 
>>> The alternative is an explicit radix tree data structure, but
>>> we may as well
>>> make use of the page-table structures to do the lookup work for us.
>>> 
>>>  -- Keir
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-devel



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