linux-kernel - Re: Specific support for Intel Atom architecture

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a36005b50905140638r56f73095kfc669bae1333e2bd@mail.gmail.com>
Date:	Thu, 14 May 2009 06:38:48 -0700
From:	Ulrich Drepper <drepper@...il.com>
To:	Harvey Harrison <harvey.harrison@...il.com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Tobias Doerffel <tobias.doerffel@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Specific support for Intel Atom architecture

On Wed, May 13, 2009 at 10:04 PM, Harvey Harrison
<harvey.harrison@...il.com> wrote:
> It's called be16_to_cpup, or on x86, swab16p()

Indeed.  If now somebody with an Atom could test whether using movbe
has an advantage (my guess is that there is a slight advantage) then
one could define a special version of the __beXX_to_cpup and
__cpu_to_beXXp functions for Atom and start using these functions more
rigorously in the tree.
--
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/