From: Johannes Berg <johannes@sipsolutions.net>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, sam <sam@ravnborg.org>
Subject: Re: [PATCH] introduce HAVE_EFFICIENT_UNALIGNED_ACCESS Kconfig symbol
Date: Wed, 09 Apr 2008 15:43:43 +0200 [thread overview]
Message-ID: <1207748623.7442.14.camel@johannes.berg> (raw)
In-Reply-To: <200804082111.35944.zippel@linux-m68k.org>
[-- Attachment #1: Type: text/plain, Size: 752 bytes --]
Hi,
> Please CC linux-arch@vger.kernel.org for such changes, so it's more likely
> noticed by more arch maintainers, so a list can be compiled what is
> appropriate for the various archs.
Hah. I thought there was such a list but it didn't show up in
MAINTAINERS so I thought I was wrong.
> The scope of this symbol is IMO a little unclear, is it intended for one-time
> accesses to small object or also for repeated accesses to larger objects?
> Anyway, this probably should be set for m68k as well.
Also for repeated accesses, for example network packets where the IPv4
header might not always be aligned. That's why we want it to be
"efficient", not just "possible" (as an earlier version of the patch
called it.)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2008-04-09 13:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 15:05 [PATCH] introduce HAVE_EFFICIENT_UNALIGNED_ACCESS Kconfig symbol Johannes Berg
2008-04-08 15:41 ` Stefan Richter
2008-04-08 16:00 ` Johannes Berg
2008-04-08 16:03 ` [PATCH v6] " Johannes Berg
2008-04-08 19:11 ` [PATCH] " Roman Zippel
2008-04-09 13:43 ` Johannes Berg [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-07 21:05 Johannes Berg
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=1207748623.7442.14.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.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