| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <20080320.141307.173590705.davem@davemloft.net> Date: Thu, 20 Mar 2008 14:13:07 -0700 (PDT) From: David Miller <davem@...emloft.net> To: johannes@...solutions.net Cc: sam@...nborg.org, dsd@...too.org, linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org, netdev@...r.kernel.org Subject: Re: [PATCH/RFC v2] introduce ARCH_CAN_UNALIGNED_ACCESS Kconfig symbol From: Johannes Berg <johannes@...solutions.net> Date: Thu, 20 Mar 2008 19:39:33 +0100 > In many cases, especially in networking, it can be beneficial to > know at compile time whether the architecture can do unaligned > accesses. This patch introduces a new Kconfig symbol > ARCH_CAN_UNALIGNED_ACCESS > for that purpose and adds it to the powerpc and x86 architectures. > Also add some documentation about alignment and networking, and > especially one intended use of this symbol. > > Signed-off-by: Johannes Berg <johannes@...solutions.net> 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists