I'm a bit disappointed that the FPU memcpy() does poorly on this
system. When I cranked the system clock to 83 MHz (with a 2.5
multiplier -- this is about 208 MHz on the chip), I was finally able
to get the FPU memcpy() to roughly match the performance I got on a
P90 with 60 ns (X-3-3-3 timing, to be sure) on a Neptune motherboard
-- about 43 MB/sec. On the other hand, rep movsd was reasonably fast
(about 60 MB/sec).
I have another problem -- I accidentally tanked my cvs repository for
Linux kernels. I'm in the process of reconstructing it, but I haven't
had a lot of time to put into that, so I'm not going to have much
chance to put together new patches any time soon.
Good news from the upgrade: the Linux side of my box upgraded
seamlessly (other than some annoying warnings from the 2.0.30 kernel
about unknown PCI chips -- it doesn't know about the TX chipset). The
Windows 95 side was another matter altogether. It wouldn't boot at
all, so I reinstalled Windows, then I started to reinstall drivers.
After (I think) I reinstalled the Symbios 810 driver, it wouldn't boot
again! I had to reinstall Windows again, and had a lot of grief
trying to reload the Matrox Millennium driver. Right now things are
working, except for dialup networking (for some reason it isn't
picking up on the dialup scripting that I need). Feh.
I still have a 4GB 'Cuda to install, to eventually replace the 2GB
Hawk that I have that's showing some thermal problems (and to speed
the thing up).
Overall, it's about a 3x boost, based on the kernel compile test.
Plus, the Gimp runs somewhat faster now.
Would anyone like to take over maintenance of the FPU patch, seeing as
though I'm not going to be using it with the AMD? I'm happy to keep
maintaining it, but I probably won't have a chance to do very much on
a regular basis.
-- Robert Krawitz <rlk@torrent.com> Founding Engineer Torrent Systems Inc. 617-354-8484x104