From: Seth Goldberg <bergsoft@home.com>
To: linux-kernel@vger.kernel.org
Subject: Athlon and fast_page_copy: What's it worth ? :)
Date: Fri, 04 May 2001 22:03:57 -0700 [thread overview]
Message-ID: <3AF389BD.81F9B398@home.com> (raw)
In-Reply-To: <E14vmpN-000822-00@the-village.bc.nu> <006e01c0d4e9$3c0bd210$0300a8c0@methusela> <20010504172657.B14969@debian.org> <20010505155113.D29451@metastasis.f00f.org> <3AF37CD6.17677C56@home.com> <20010505163204.A29622@metastasis.f00f.org>
Hi,
Before I go any further with this investigation, I'd like to get an
idea
of how much of a performance improvement the K7 fast_page_copy will give
me.
Can someone suggest the best benchmark to test the speed of this
routine?
Thanks,
Seth
next prev parent reply other threads:[~2001-05-05 5:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-04 17:22 REVISED: Experimentation with Athlon and fast_page_copy Seth Goldberg
2001-05-04 19:48 ` Brian Gerst
2001-05-04 21:09 ` Alan Cox
2001-05-04 22:26 ` Aaron Tiensivu
2001-05-04 18:10 ` Bobby D. Bryant
2001-05-05 6:43 ` John R Lenton
2001-05-05 7:20 ` Alan Cox
2001-05-07 1:26 ` John R Lenton
2001-05-07 1:30 ` Jeremy
2001-05-05 0:26 ` Joseph Carter
2001-05-05 3:51 ` Chris Wedgwood
2001-05-05 4:08 ` Seth Goldberg
[not found] ` <20010505163204.A29622@metastasis.f00f.org>
2001-05-05 5:03 ` Seth Goldberg [this message]
2001-05-05 6:20 ` Athlon and fast_page_copy: What's it worth ? :) Mark Hahn
2001-05-05 9:15 ` Tom Leete
2001-05-05 7:17 ` Alan Cox
2001-05-05 14:19 ` Jonathan Morton
2001-05-05 14:41 ` Alan Cox
2001-05-05 15:17 ` Jonathan Morton
2001-05-08 21:16 ` Arjan van de Ven
2001-05-05 5:45 ` REVISED: Experimentation with Athlon and fast_page_copy Joseph Carter
2001-05-09 2:11 ` Tom Leete
2001-05-09 8:49 ` Alan Cox
2001-05-09 11:38 ` Tom Leete
2001-05-09 12:38 ` Alan Cox
2001-05-09 13:02 ` Tom Leete
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=3AF389BD.81F9B398@home.com \
--to=bergsoft@home.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