From: Randolph Chung <randolph@tausq.org>
To: Carlos O'Donell <carlos@baldric.uwo.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] [RFC] Optimi[zs]e copy_*_user routines
Date: Fri, 17 Sep 2004 08:34:39 -0700 [thread overview]
Message-ID: <20040917153439.GI28659@tausq.org> (raw)
In-Reply-To: <20040917144813.GH28936@baldric.uwo.ca>
> What tests have you run against this?
> I think the original version was pretty stable on my 32-bit UP c3k.
> Included kernel compiles and some lws tests.
i've done kernel compiles at various -j levels, and run some lmbench
benchmarks.
as you know, there's also a memcpy testsuite that verified the main
copying algorithm for various block sizes and alignments.
i also have a small test program that is able to exercise the
exception cases in the code, so i've tested the various load/store
exception cases in the two functions (pa_memcpy and copy_dstaligned).
currently, the exception test program is a bit indirect (it requires a
lot of manual work). i have an idea for a better automated testsuite
which still needs to be implemented.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2004-09-17 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 0:00 [parisc-linux] [RFC] Optimi[zs]e copy_*_user routines Randolph Chung
2004-09-10 0:15 ` Randolph Chung
2004-09-10 14:04 ` Carlos O'Donell
[not found] ` <200409100656.i8A6u4hI026343@hiauly1.hia.nrc.ca>
2004-09-10 8:14 ` Randolph Chung
2004-09-10 8:46 ` John David Anglin
2004-09-16 19:18 ` Randolph Chung
[not found] ` <20040917144813.GH28936@baldric.uwo.ca>
2004-09-17 15:34 ` Randolph Chung [this message]
2004-09-17 16:23 ` Carlos O'Donell
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=20040917153439.GI28659@tausq.org \
--to=randolph@tausq.org \
--cc=carlos@baldric.uwo.ca \
--cc=parisc-linux@lists.parisc-linux.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