public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Jens Maurer <Jens.Maurer@gmx.net>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Use x86 SSE instructions for clear_page, copy_page
Date: Tue, 17 Aug 2004 10:11:07 +0200	[thread overview]
Message-ID: <20040817081107.GA12690@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040817081009.GA806@pazke>

[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]

On Tue, Aug 17, 2004 at 12:10:09PM +0400, Andrey Panin wrote:
> On 230, 08 17, 2004 at 09:27:51AM +0200, 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.
> > > 
> > > A user-space test on my Pentium III 850 MHz shows a 3x speedup for
> > > clear_page (compared to the default "rep stosl"), and a 50% speedup
> > > for copy_page (compared to the default "rep movsl").  For a Pentium-4,
> > > the speedup is about 50% in both the clear_page and copy_page cases.
> > 
> > 
> > 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 ;(
> 
> Did SSE clear_page() suffered from this issue too ?

yes especially clear_page; the kernel only calls clear_page when it's *just
about* to use it, so it's actually the worst case example ;(

(and clear_page gains the most because non-temperal stores avoid the write
allocate so it like halves the memory bandwidth)

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-08-17  8:13 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 [this message]
2004-08-17 22:40   ` Jens Maurer
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=20040817081107.GA12690@devserv.devel.redhat.com \
    --to=arjanv@redhat.com \
    --cc=Jens.Maurer@gmx.net \
    --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