On Nov 23, 2007, at 5:43 AM, Heikki Orsila wrote:
On Fri, Nov 23, 2007 at 12:15:53AM +0000, Daniel Drake wrote:
Why unaligned access is bad
===========================
Most architectures are unable to perform unaligned memory accesses.
Any
unaligned access causes a processor exception.
"Some architectures are unable to perform unaligned memory accesses,
either an exception is generated, or the data
access is silently invalid. In architectures that allow unaligned
access, natural aligned accesses are usually faster than non-aligned."
In summary: if your code causes unaligned memory accesses to
happen, your code
will not work on some platforms, and will perform *very* badly on
others.
*very* -> *slower*
Natural alignment
=================
Please move this definition before "Why unaligned access is bad".
Also, it would be nice to have a table of ISAs:
ISA Need Need
natural alignment
alignment by x
--------------------------------------------
m68k No 2
powerpc/ppc Yes Word size
on ppc it varies from processor to processor if misaligned data is
fixed up or causes an exception. However its highly recommend to be
naturally aligned. I'm not sure I follow what is meant by the second
column (need alignment by x).
- k
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
