mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: David Miller <davem@davemloft.net>
Cc: sam@ravnborg.org, dsd@gentoo.org, linux-kernel@vger.kernel.org,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH/RFC v2] introduce ARCH_CAN_UNALIGNED_ACCESS Kconfig symbol
Date: Thu, 20 Mar 2008 22:21:46 +0100	[thread overview]
Message-ID: <1206048106.16475.161.camel@johannes.berg> (raw)
In-Reply-To: <20080320.141307.173590705.davem@davemloft.net>

[-- Attachment #1: Type: text/plain, Size: 682 bytes --]


> I think you're semantically testing the wrong thing.
> 
> It's not if unaligned accesses are supported, it's if they are
> efficient enough or not.
> 
> For example, sparc64 fully handles unaligned accesses but taking the
> trap to fix it up is slow.  So sparc64 "can" handle unaligned
> accesses, but whether we want to set this symbol or not is another
> matter.

Yeah, good point. Should I rename it to HAVE_EFFICIENT_UNALIGNED_ACCESS
or similar? Or have it defined as some sort of number so you can make
actually make tradeoffs? Like Dave Woodhouse suggested at some point to
have get_unaligned() take an argument that indicates the probability...

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2008-03-20 21:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20 14:34 [PATCH/RFC] " Johannes Berg
2008-03-20 14:39 ` Will Newton
2008-03-20 14:58   ` Johannes Berg
2008-03-20 18:13 ` Sam Ravnborg
2008-03-20 18:35   ` Johannes Berg
2008-03-20 18:39   ` [PATCH/RFC v2] " Johannes Berg
2008-03-20 18:45     ` [PATCH/RFC v3] " Johannes Berg
2008-03-20 19:09       ` Harvey Harrison
2008-03-20 19:12         ` Johannes Berg
2008-03-20 19:41       ` Sam Ravnborg
2008-03-20 19:50         ` [PATCH/RFC v4] introduce HAVE_UNALIGNED_ACCESS_SUPPORT " Johannes Berg
2008-03-21  8:45           ` Ingo Molnar
2008-03-20 21:13     ` [PATCH/RFC v2] introduce ARCH_CAN_UNALIGNED_ACCESS " David Miller
2008-03-20 21:21       ` Johannes Berg [this message]
2008-03-20 21:27         ` David Miller
2008-03-20 22:03         ` John W. Linville
2008-03-20 22:10           ` David Miller
2008-03-25 14:11       ` [PATCH/RFC v5] introduce HAVE_EFFICIENT_UNALIGNED_ACCESS " Johannes Berg
2008-04-02 10:24         ` 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=1206048106.16475.161.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=davem@davemloft.net \
    --cc=dsd@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sam@ravnborg.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®