mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Heikki Orsila <shdl@zakalwe.fi>
Cc: Daniel Drake <dsd@gentoo.org>,
	linux-kernel@vger.kernel.org, davem@davemloft.net,
	kune@deine-taler.de, johannes@sipsolutions.net
Subject: Re: [RFC] Documentation about unaligned memory access
Date: Sun, 25 Nov 2007 12:16:08 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0711251215380.5532@anakin> (raw)
In-Reply-To: <20071123114329.GG7681@zakalwe.fi>

On Fri, 23 Nov 2007, 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

`No' for >= 68020.
`Yes' for < 68020.

> powerpc/ppc	Yes		Word size
> x86		No		No
> x86_64		No		No

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

  reply	other threads:[~2007-11-25 11:16 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-23  0:15 Daniel Drake
2007-11-23  0:27 ` Avuton Olrich
2007-11-23  1:29 ` Alan Cox
2007-11-23  3:04   ` Kyle Moffett
2007-11-23  6:18   ` dean gaudet
2007-11-23  9:46     ` Arne Georg Gleditsch
2007-11-26 14:50       ` dean gaudet
2007-11-23  1:29 ` David Miller
2007-11-23 10:06 ` Jan Engelhardt
2007-11-23 11:43 ` Heikki Orsila
2007-11-25 11:16   ` Geert Uytterhoeven [this message]
2007-11-25 11:24     ` Heikki Orsila
2007-11-26  0:48       ` Alan Cox
2007-11-26 17:12   ` Ben Dooks
2007-11-27  7:51   ` Kumar Gala
2007-11-23 22:02 ` Vadim Lobanov
2007-11-23 22:52 ` Dmitri Vorobiev
2007-11-24 13:34 ` Pierre Ossman
2007-11-24 15:50   ` Luciano Rocha
2007-11-24 16:19     ` Pierre Ossman
2007-11-24 17:22       ` Luciano Rocha
2007-11-24 17:35         ` Pierre Ossman
2007-11-24 18:28           ` Luciano Rocha
2007-11-24 17:53         ` Haavard Skinnemoen
2007-11-25  8:27 ` Denys Vlasenko
2007-11-25 14:13 ` Olaf Titz
2007-11-26  9:14 ` DM
2007-11-26 14:47 ` Johannes Berg
2007-11-27  0:40   ` Arnaldo Carvalho de Melo
2007-11-26 14:51 ` Johannes Berg
2007-11-30  8:18 ` Jörn Engel
     [not found] <fa.U+CIv4JClOmn6KppLkEOSk7RW0Y@ifi.uio.no>
2007-11-23  1:24 ` Robert Hancock
2007-11-23  2:07   ` Andi Kleen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0711251215380.5532@anakin \
    --to=geert@linux-m68k.org \
    --cc=davem@davemloft.net \
    --cc=dsd@gentoo.org \
    --cc=johannes@sipsolutions.net \
    --cc=kune@deine-taler.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shdl@zakalwe.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®