public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Rainer Keller <Keller@hlrs.de>
Cc: linux-kernel@vger.kernel.org, Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: [PATCH] Small optimization for UP in sched and prefetch
Date: Fri, 11 Jan 2002 05:51:14 -0500	[thread overview]
Message-ID: <3C3EC3A2.C9C9D184@mandrakesoft.com> (raw)
In-Reply-To: <3C3EBF76.3AEB82AB@hlrs.de>

Rainer Keller wrote:
> PS: Because of usage of prefetch in include/linux/list.h, the memory
> prefetch is triggered 137 times on my configuration...

We need to merge in __builtin_prefetch support into the kernel, because
gcc 3.1 recently got support for it.  It would be nice at least for
future prefetch-related patches to perhaps call __builtin_prefetch, and
have the headers substitute a prefetch if the compiler does not support
it.

	Jeff



-- 
Jeff Garzik      | Alternate titles for LOTR:
Building 1024    | Fast Times at Uruk-Hai
MandrakeSoft     | The Took, the Elf, His Daughter and Her Lover
                 | Samwise Gamgee: International Hobbit of Mystery

  reply	other threads:[~2002-01-11 10:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-11 10:33 [PATCH] Small optimization for UP in sched and prefetch Rainer Keller
2002-01-11 10:51 ` Jeff Garzik [this message]
2002-01-11 17:07   ` [PATCH] Small optimization for UP in sched and prefetch (take 3) Rainer Keller
2002-01-11 19:59 ` [PATCH] Small optimization for UP in sched and prefetch Robert Love
2002-01-11 20:02   ` Dave Jones
2002-01-11 20:07     ` Robert Love

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=3C3EC3A2.C9C9D184@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=Keller@hlrs.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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