From: "David S. Miller" <davem@redhat.com>
To: Jens Maurer <Jens.Maurer@gmx.net>
Cc: linux-kernel@vger.kernel.org, arjanv@redhat.com
Subject: Re: [PATCH] Use x86 SSE instructions for clear_page, copy_page
Date: Tue, 17 Aug 2004 19:33:38 -0700 [thread overview]
Message-ID: <20040817193338.16f57197.davem@redhat.com> (raw)
In-Reply-To: <41228946.5040207@gmx.net>
On Wed, 18 Aug 2004 00:40:06 +0200
Jens Maurer <Jens.Maurer@gmx.net> wrote:
> What is a set of useful benchmarks to find out which approach
> is better?
Time kernel builds on an otherwise totally idle machine.
Do multiple runs so that the cache gets loaded and you're
testing the memory accesses rather than disk reads.
next prev parent reply other threads:[~2004-08-18 2:36 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 [this message]
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=20040817193338.16f57197.davem@redhat.com \
--to=davem@redhat.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox