From: GrandMasterLee <masterlee@digitalroadkill.net>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Dave Jones <davej@codemonkey.org.uk>,
Linux-Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19/20, 2.5 missing P4 ifdef ?
Date: 28 Nov 2002 22:51:05 -0600 [thread overview]
Message-ID: <1038545465.25442.7.camel@UberGeek> (raw)
In-Reply-To: <Pine.LNX.3.96.1021128121018.12997B-100000@gatekeeper.tmr.com>
On Thu, 2002-11-28 at 11:12, Bill Davidsen wrote:
> On Thu, 28 Nov 2002, Dave Jones wrote:
>
> > On Thu, Nov 28, 2002 at 03:17:53PM +0100, Margit Schubert-While wrote:
> > > Just noticed this in "include/asm-i386/processor.h" :
> > >
> > > --- snip ---
> > > /* Prefetch instructions for Pentium III and AMD Athlon */
> > > #ifdef CONFIG_MPENTIUMIII
> > > #define ARCH_HAS_PREFETCH
> > > extern inline void prefetch(const void *x)
> > > {
> > > __asm__ __volatile__ ("prefetchnta (%0)" : : "r"(x));
> > > }
> > > #elif CONFIG_X86_USE_3DNOW
> > > --- end snip ---
> > >
> > > The P4 has SSE and prefetch or no ?
> >
> > It does. You seem to have found a bug.
>
> A bug? An inefficiency, obviously, but it should be functionally correct,
> no? Or is there a problem I've missed other than performance?
IMHO, when building systems, any deficiency I find, is logged as a bug.
I'd imagine, anything perceived as a problem, should be treated this
way. Imho, performance, or lack of, is a bug, if a potential fix is
available.
--The GrandMaster
next prev parent reply other threads:[~2002-11-29 4:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 14:17 2.4.19/20, 2.5 missing P4 ifdef ? Margit Schubert-While
2002-11-28 14:24 ` Dave Jones
2002-11-28 17:12 ` Bill Davidsen
2002-11-29 4:51 ` GrandMasterLee [this message]
2002-11-29 0:08 ` J.A. Magallon
2002-12-02 13:24 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2002-11-29 7:42 Margit Schubert-While
2002-12-03 9:01 Margit Schubert-While
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=1038545465.25442.7.camel@UberGeek \
--to=masterlee@digitalroadkill.net \
--cc=davej@codemonkey.org.uk \
--cc=davidsen@tmr.com \
--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