From: "H. Peter Anvin" <hpa@zytor.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Johannes Berg <johannes@sipsolutions.net>,
dsd@gentoo.org, davem@davemloft.net, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org
Subject: Re: wireless vs. alignment requirements
Date: Tue, 27 Nov 2007 18:42:26 -0800 [thread overview]
Message-ID: <474CD592.2020108@zytor.com> (raw)
In-Reply-To: <20071127103940.314c7844@freepuppy.rosehill>
Stephen Hemminger wrote:
>
> Is there any standard kernel config define for "this platform can't do
> unaligned accesses"?
>
Not that I know of, but there should be.
To be somewhat more complexicated, some platforms (e.g. MIPS) can do
unaligned references quite cheaply, but they need different opcodes to
do so.
-hpa
next prev parent reply other threads:[~2007-11-28 2:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071123000922.C44009D4A1F@zog.reactivated.net>
2007-11-23 20:33 ` wireless vs. alignment requirements Johannes Berg
2007-11-24 6:15 ` Herbert Xu
2007-11-24 8:33 ` Johannes Berg
2007-11-24 13:32 ` Herbert Xu
2007-11-24 13:49 ` Johannes Berg
2007-11-24 13:51 ` David Miller
2007-11-24 14:13 ` Herbert Xu
2007-11-24 20:11 ` Stephen Hemminger
2007-11-24 21:33 ` Johannes Berg
2007-11-25 1:08 ` Herbert Xu
2007-11-25 21:21 ` Stephen Hemminger
2007-11-26 1:38 ` Herbert Xu
2007-11-27 17:16 ` H. Peter Anvin
2007-11-27 17:16 ` H. Peter Anvin
2007-11-27 18:39 ` Stephen Hemminger
2007-11-28 2:42 ` H. Peter Anvin [this message]
2007-11-29 13:11 ` Herbert Xu
2007-11-29 17:50 ` H. Peter Anvin
2007-11-30 0:26 ` Herbert Xu
2007-11-30 0:28 ` H. Peter Anvin
2007-11-30 0:34 ` Herbert Xu
2007-11-30 0:41 ` H. Peter Anvin
2007-11-24 21:13 ` Johannes Berg
2007-11-25 1:44 ` Herbert Xu
2007-11-25 11:00 ` Johannes Berg
2007-11-25 11:22 ` Herbert Xu
2007-11-25 13:54 ` Johannes Berg
2007-11-25 14:01 ` Herbert Xu
2007-11-25 17:04 ` Johannes Berg
2007-11-26 1:36 ` Herbert Xu
2007-11-24 13:11 ` Ulrich Kunitz
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=474CD592.2020108@zytor.com \
--to=hpa@zytor.com \
--cc=davem@davemloft.net \
--cc=dsd@gentoo.org \
--cc=herbert@gondor.apana.org.au \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@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;
as well as URLs for NNTP newsgroup(s).