| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] __ia64__ ifdef in xmalloc.c: "Fix ar.unat handling forfa
|
To: |
"Tian, Kevin" <kevin.tian@xxxxxxxxx> |
|
Subject: |
Re: [Xen-devel] __ia64__ ifdef in xmalloc.c: "Fix ar.unat handling forfast paths" |
|
From: |
David Mosberger-Tang <David.Mosberger@xxxxxxx> |
|
Date: |
Wed, 23 Nov 2005 08:30:59 -0800 |
|
Cc: |
"Luck, Tony" <tony.luck@xxxxxxxxx>, linux-ia64@xxxxxxxxxxxxxxx, Rusty Russell <rusty@xxxxxxxxxxxxxxx>, Tony Breeds <tony@xxxxxxxxxxxxxxxxxx>, djm@xxxxxxxxxxxxxxx, Xen Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|
Delivery-date: |
Thu, 24 Nov 2005 00:00:17 +0000 |
|
Domainkey-signature: |
a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=B3h/D29KOdK9AxFAkmTZ1aDFEiekYBO5e3cfgdTtb8ZzHMM//wWqD6xHSEarXvib5hxg7NwFw/6Rcr9ApQkIn6EiiRe7wDFnFPAyfH0yuwIhoI2VYgNYW5kY/u2YIEfuqvZKJ1+ctRXYea/7TsI/9JVCj8WmB9tVrm3iH+pJ8r8= |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<571ACEFD467F7749BC50E0A98C17CDD802C069E3@pdsmsx403> |
|
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> |
|
References: |
<571ACEFD467F7749BC50E0A98C17CDD802C069E3@pdsmsx403> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
On 11/22/05, Tian, Kevin <kevin.tian@xxxxxxxxx> wrote:
> Now I think even '16' can't cover all cases. It's possible for a user defined
> structure with .align directive to force by '32' or larger, and then
> allocator happens to have similar check upon SMP_CACHE_BYTES like case in
> this thread. Because both structure definition and allocator may have no idea
> about IA64 trick of saving space for UP. Max alignment of any C style only
> solves the natural alignment case, but not above forced one. We can just give
> its real assumption to SMP_CACHE_BYTES - cache line size. ;-)
Not likely to be a problem. Memory allocators generally guarantee
only 16-byte alignment (as per ia64 software conventions).
--david
--
Mosberger Consulting LLC, voice/fax: 510-744-9372,
http://www.mosberger-consulting.com/
35706 Runckel Lane, Fremont, CA 94536
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
| <Prev in Thread] |
Current Thread |
[Next in Thread>
|
- RE: [Xen-devel] __ia64__ ifdef in xmalloc.c: "Fix ar.unat handling forfast paths", Tian, Kevin
- RE: [Xen-devel] __ia64__ ifdef in xmalloc.c: "Fix ar.unat handling forfast paths", Tian, Kevin
- RE: [Xen-devel] __ia64__ ifdef in xmalloc.c: "Fix ar.unat handling forfast paths", Tian, Kevin
- RE: [Xen-devel] __ia64__ ifdef in xmalloc.c: "Fix ar.unat handling forfast paths", Magenheimer, Dan (HP Labs Fort Collins)
- RE: [Xen-devel] __ia64__ ifdef in xmalloc.c: "Fix ar.unat handling forfast paths", Luck, Tony
- RE: [Xen-devel] __ia64__ ifdef in xmalloc.c: "Fix ar.unat handling forfast paths", Luck, Tony
|
|
|
| |
|
Home