public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jens Maurer <Jens.Maurer@gmx.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	Arjan van de Ven <arjanv@redhat.com>
Subject: Re: [PATCH] Use x86 SSE instructions for clear_page, copy_page
Date: Wed, 18 Aug 2004 09:11:12 +0200	[thread overview]
Message-ID: <20040818071112.GA11543@elte.hu> (raw)
In-Reply-To: <20040818070013.GA11048@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> executed SSE code? You are corrupting those registers.

doh - should read before i write. The code is perfectly fine.

Arjan's cache arguments remain. What i'd suggest to test is the precise
speed of compiling the kernel, fully done in ramfs. (if you dont have
enough RAM for this then compile a portion of the kernel.) For the
testing, add a /proc/sys switch to turn the SSE functions on/off
runtime, hence you can eliminate the effects of page placement. If the
compilation timings are stable enough then you can try the runtime
switch to see whether it has any effect. There should be a small but
visible change (in one direction or the other), as compilation brings in
lots of new pages and copies around stuff too.

	Ingo

      reply	other threads:[~2004-08-18  7:09 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
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 [this message]

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=20040818071112.GA11543@elte.hu \
    --to=mingo@elte.hu \
    --cc=Jens.Maurer@gmx.net \
    --cc=akpm@osdl.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox