From: Ulrich Drepper <drepper@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Why ssse3?
Date: Wed, 02 May 2007 15:56:26 -0700 [thread overview]
Message-ID: <4639171A.3050004@redhat.com> (raw)
In-Reply-To: <200705030046.07152.ak@suse.de>
[-- Attachment #1: Type: text/plain, Size: 383 bytes --]
Andi Kleen wrote:
> Nope. SSE3 != SSSE3. The additional S means Supplemential.
>
> It's probably because the few changes didn't justify a SSE4
OK, the problem is that the actual sse3 bit is misnamed. According to
Intel's docs bit 0 of ECX is "sse", the kernel uses "pni". Too bad.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next prev parent reply other threads:[~2007-05-02 22:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 22:41 Why ssse3? Ulrich Drepper
2007-05-02 22:46 ` Andi Kleen
2007-05-02 22:56 ` Ulrich Drepper [this message]
2007-05-03 2:28 ` H. Peter Anvin
2007-05-03 8:52 ` Andi Kleen
2007-05-03 9:02 ` Avi Kivity
2007-05-03 9:07 ` Andi Kleen
2007-05-03 16:03 ` Roland Dreier
2007-05-02 22:47 ` Ismail Dönmez
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=4639171A.3050004@redhat.com \
--to=drepper@redhat.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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