From: David Howells <dhowells@redhat.com>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: dhowells@redhat.com, Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 2/2] kernel: Move arches to use common unaligned access
Date: Fri, 11 Apr 2008 11:11:28 +0100 [thread overview]
Message-ID: <15208.1207908688@redhat.com> (raw)
In-Reply-To: <1207885132.22001.85.camel@brick>
Harvey Harrison <harvey.harrison@gmail.com> wrote:
> -#ifndef _ASM_UNALIGNED_H
> -#define _ASM_UNALIGNED_H
> -
> +#ifndef _ASM_FRV_UNALIGNED_H_
> +#define _ASM_FRV_UNALIGNED_H_
Why?
> - * impractical. So, now we fall back to using memcpy.
> + * impractical. So, now we fall back to using memmov.
That's memmove, not memmov. Any why memmove, not memcpy? Is __tmp likely to
overlap with *ptr?
Also, for FRV, I think calling memmove/memcpy for MMU kernels may be the wrong
thing to do... I'm sort of leaning towards doing the same thing as NOMMU
kernels and just using your inline ones.
The advantage of the inline ones is that they are quicker and probably involve
fewer instructions executed; whereas using memcpy/memmove may end up with
smaller, but slower code. Hmmm... Maybe key on CONFIG_CC_OPTIMIZE_FOR_SIZE?
David
next prev parent reply other threads:[~2008-04-11 10:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 3:38 [PATCH 2/2] kernel: Move arches to use common unaligned access Harvey Harrison
2008-04-11 7:48 ` Ingo Molnar
2008-04-11 10:11 ` David Howells [this message]
2008-04-11 10:16 ` David Miller
2008-04-11 10:27 ` David Howells
2008-04-11 15:19 ` Harvey Harrison
2008-04-11 15:50 ` David Howells
2008-04-11 17:31 ` Harvey Harrison
2008-04-11 17:55 ` [PATCH 2/2-revised] " Harvey Harrison
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=15208.1207908688@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=harvey.harrison@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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