All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Maurer <Jens.Maurer@gmx.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: arjanv@redhat.com
Subject: Re: [PATCH] Use x86 SSE instructions for clear_page, copy_page
Date: Wed, 18 Aug 2004 00:40:06 +0200	[thread overview]
Message-ID: <41228946.5040207@gmx.net> (raw)
In-Reply-To: <1092727670.2792.4.camel@laptop.fenrus.com>


Arjan van de Ven wrote:
> On Tue, 2004-08-17 at 08:13, Jens Maurer wrote:
> 
>>The attached patch (against kernel 2.6.8.1) enables using SSE
>>instructions for copy_page and clear_page.

> we used to have code like this in 2.4 but it got removed: the non
> temperal store code is faster in a microbenchmark but has the
> fundamental problem that it evics the data from the cpu cache; the
> actual USE of the data thus is a LOT more expensive, result is that the
> overall system performance goes down ;(

Hm... With the current clear_page, we are filling 4KB of my
Pentium-III's 16 KB L1 d-cache (i.e. 25%) with zeroes.  I'm not
sure that we will use all of this data right away.

I would like to point out that the current arch/i386/lib/mmx.c
uses MMX movntq instructions #ifdef CONFIG_MK7 .
Apparently, bypassing the cache was considered a good idea
in that case.

What is a set of useful benchmarks to find out which approach
is better?  We should have some real-world programs that show
significant oprofile hits in clear_page or copy_page.
It might very well be that the results on Pentium-III and
Pentium-4 are different, for example that SSE is only useful
for a Pentium-III, and only for clear_page.

Jens Maurer


  parent reply	other threads:[~2004-08-17 22:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-17  6:13 [PATCH] Use x86 SSE instructions for clear_page, copy_page Jens Maurer
2004-08-17  7:27 ` Arjan van de Ven
2004-08-17  8:10   ` Andrey Panin
2004-08-17  8:11     ` Arjan van de Ven
2004-08-17 22:40   ` Jens Maurer [this message]
2004-08-18  2:33     ` David S. Miller
2004-08-22 20:49       ` Jens Maurer
2004-08-18  7:00 ` Ingo Molnar
2004-08-18  7:11   ` Ingo Molnar

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=41228946.5040207@gmx.net \
    --to=jens.maurer@gmx.net \
    --cc=arjanv@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.