Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


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

Re: I think I'm ready to give up on x86_64



 Jerry Feldman wrote: 
> On Sun, 28 Oct 2007 07:56:13 -0400 
> Nathan Meyers <[hidden email]> wrote: 
> 
>   
>> 64 bits also places higher demands on the 
>> system: more bits to sling around the bus and greater load on the heap 
>> from the larger words. Unless you need that address space, moving to 64 
>> bits is pure downside. 
>>     
> 
> The incremental load on the bus is small if anything since it is 
> designed for 64 bits. Why is there an extra load on the heap. The heap 
> would be allocated on a 64-bit boundary, but malloc will allocate what 
> you need. But, yes, because of boundary conditions, structures are 
> aligned on 64-bit boundaries. So, your code may use some extra memory. 
> On the upside, as I mentioned there are 16 64-bit registers. While this 
> means saving more registers on context switches, it can mean better 
> performance. 
>   


BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org