[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] ia64 ifdef in xmalloc.c: "Fix ar.unat handling forfast paths"

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, "Tian, Kevin" <kevin.tian@xxxxxxxxx>
From: "Luck, Tony" <tony.luck@xxxxxxxxx>
Date: Wed, 23 Nov 2005 07:07:49 -0800
Cc: Xen Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>, linux-ia64@xxxxxxxxxxxxxxx, Rusty Russell <rusty@xxxxxxxxxxxxxxx>, Tony Breeds <tony@xxxxxxxxxxxxxxxxxx>, djm@xxxxxxxxxxxxxxx, David Mosberger-Tang <David.Mosberger@xxxxxxx>
Delivery-date: Thu, 24 Nov 2005 00:00:51 +0000
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Thread-index: AcXwDmS/56OkMzn6Rb2y1vOGnL1rKQAMQsXg
Thread-topic: [Xen-devel] __ia64__ ifdef in xmalloc.c: "Fix ar.unat handling forfast paths"

>It's not hard to support arbitrary alignment, at the cost of burning 
>some space. We should probably do that.

The "we" in that last sentence is the Xen team ... referring
to making fixes to xmalloc?

-Tony

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

Follow-Ups:
- Re: [Xen-devel] __ia64__ ifdef in xmalloc.c: "Fix ar.unat handling forfast paths"
  - From: Keir Fraser

Prev by Date: Re: [Xen-devel] __ia64__ ifdef in xmalloc.c: "Fix ar.unat handling forfast paths"
Next by Date: [Xen-devel] [PATCH] dom0_ops -EPERM not -EACCES?
Previous by thread: RE: [Xen-devel] __ia64__ ifdef in xmalloc.c: "Fix ar.unat handling forfast paths"
Next by thread: Re: [Xen-devel] __ia64__ ifdef in xmalloc.c: "Fix ar.unat handling forfast paths"
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.

RE: [Xen-devel] __ia64__ ifdef in xmalloc.c: "Fix ar.unat handling forfast paths"

RE: [Xen-devel] ia64 ifdef in xmalloc.c: "Fix ar.unat handling forfast paths"