mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@logfs.org>
To: Daniel Drake <dsd@gentoo.org>
Cc: linux-kernel@vger.kernel.org, davem@davemloft.net,
	kune@deine-taler.de, johannes@sipsolutions.net
Subject: Re: [RFC] Documentation about unaligned memory access
Date: Fri, 30 Nov 2007 09:18:35 +0100	[thread overview]
Message-ID: <20071130081835.GA28414@lazybastard.org> (raw)
In-Reply-To: <20071123001554.12F8B9D4A1F@zog.reactivated.net>

On Fri, 23 November 2007 00:15:53 +0000, Daniel Drake wrote:
> 
> What's the definition of an unaligned access?
> =============================================
> 
> Unaligned memory accesses occur when you try to read N bytes of data starting
> from an address that is not evenly divisible by N (i.e. addr % N != 0).
> For example, reading 4 bytes of data from address 0x10000004 is fine, but
> reading 4 bytes of data from address 0x10000005 would be an unaligned memory
> access.

The wording could also apply to a DMA of 8k from a 4k-aligned address.
But I don't have a good idea how to improve it.

> It's safe to assume that memcpy will always copy bytewise and hence will
> never cause an unaligned access.

s/always copy/always behave as if copying/

memcpy usually copies at least wordwise, possibly even in bigger chunks.
But that is just the inner loop.  Unaligned bytes at the beginning/end
receive special treatment.

Jörn

-- 
The rabbit runs faster than the fox, because the rabbit is rinning for
his life while the fox is only running for his dinner.
-- Aesop

  parent reply	other threads:[~2007-11-30  8:23 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
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 [this message]
     [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=20071130081835.GA28414@lazybastard.org \
    --to=joern@logfs.org \
    --cc=davem@davemloft.net \
    --cc=dsd@gentoo.org \
    --cc=johannes@sipsolutions.net \
    --cc=kune@deine-taler.de \
    --cc=linux-kernel@vger.kernel.org \
    /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®