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] [RFC][PATCH] add tlsf option for xmalloc

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [RFC][PATCH] add tlsf option for xmalloc
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date: Wed, 15 Oct 2008 12:59:32 -0700 (PDT)
Cc: Nitin Gupta <nitingupta910@xxxxxxxxx>
Delivery-date: Wed, 15 Oct 2008 13:00:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C51BF086.1E387%keir.fraser@xxxxxxxxxxxxx>
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
> > Note that this is compile-tested but not run tested yet.  I
> > thought I'd get feedback on the approach before I get much
> > further.
> 
> The approach is fine as far as I'm concerned. It should just 
> replace the
> existing xmalloc.c of course: no point in keeping the old one around.
> Therefore may as well put the whole implementation in 
> xmalloc.c, or call it
> xmalloc_tlsf.c if you're really keen to keep the name of the 
> algorithm in
> the file name (in which case xmalloc.c should be entirely deleted; or
> perhaps temporarily make it a build option which .c file gets built if
> really worried that the new xmalloc implementation may have 
> subtle bugs and
> we'd like to be able to revert for testing).
> 
> Structure definitions and the like which are private to TLSF 
> should live at
> the top of the .c file: I prefer that to the <xen/*_int.h> 
> approach as it
> keeps private non-shared stuff all in one place.

Sounds good.

You may note that the tlsf files borrowed from Nitin Gupta use Linux-style
indentation/formatting.  One of my reasons for not merging the tlsf
allocation with xmalloc is I was too lazy to reformat ;-)  Do I need
to do that or can I leave it as is or do you have a tool that will
auto-reformat it to meet the Xen style requirements?

Thanks,
Dan

P.S. Posted patch boots fine.

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

<Prev in Thread] Current Thread [Next in Thread>