From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>,
"Justin T. Gibbs" <gibbs@scsiguy.com>,
"Linux Kernel List" <linux-kernel@vger.kernel.org>
Subject: Re: REVISED: Experimentation with Athlon and fast_page_copy
Date: Thu, 10 May 2001 01:56:54 +0200 [thread overview]
Message-ID: <01051001565400.00893@SunWave1> (raw)
In-Reply-To: <E14vwGE-0000IQ-00@the-village.bc.nu>
In-Reply-To: <E14vwGE-0000IQ-00@the-village.bc.nu>
Am Samstag, 5. Mai 2001 09:13 schrieben Sie:
> > My (very) old Athlon 550 (model 1, stepping 2) show it on my MSI MS-6167
> > (AMD Irongate C4) with your 2.4.4-ac5, now :-(
>
> Manfred has a good explanation for that. Im hoping it also explains the
> VIA problem too
>
> > I am open for any test fixes...
>
> Watch this space -> <- ;)
>
> Alan
Sorry for my noise!
My problem was NOT fast_page_copy related.
It was Justin's aic7xxx 6.1.12 release.
His latest 6.1.13 (2.4.4-ac6) fixed it for me.
My MSI MS-6167 (AMD Irongate C4) is running very well with APIC (it haven't
really have one) and ACPI (latest) enabled.
Below are some MMX copy results.
Thanks anyway.
Dieter
BTW Where can I grep the bench with MB/sec output?
SunWave1>./athlon
Athlon test program $Id: fast.c,v 1.6 2000/09/23 09:05:45 arjan Exp $
clear_page() tests
clear_page function 'warm up run' took 17396 cycles per page
clear_page function '2.4 non MMX' took 9582 cycles per page
clear_page function '2.4 MMX fallback' took 9031 cycles per page
clear_page function '2.4 MMX version' took 7905 cycles per page
clear_page function 'faster_clear_page' took 8237 cycles per page
clear_page function 'even_faster_clear' took 8151 cycles per page
copy_page() tests
copy_page function 'warm up run' took 12565 cycles per page
copy_page function '2.4 non MMX' took 17273 cycles per page
copy_page function '2.4 MMX fallback' took 17481 cycles per page
copy_page function '2.4 MMX version' took 12507 cycles per page
copy_page function 'faster_copy' took 13641 cycles per page
copy_page function 'even_faster' took 12707 cycles per page
next prev parent reply other threads:[~2001-05-09 23:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-05 2:28 REVISED: Experimentation with Athlon and fast_page_copy Dieter Nützel
2001-05-05 7:13 ` Alan Cox
2001-05-09 23:56 ` Dieter Nützel [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-05 17:34 Jeremy
2001-05-04 19:14 Manfred Spraul
2001-05-04 19:30 ` Seth Goldberg
2001-05-04 21:43 ` Alan Cox
2001-05-08 21:15 ` Arjan van de Ven
2001-05-04 17:22 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
2001-05-05 5:45 ` 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=01051001565400.00893@SunWave1 \
--to=dieter.nuetzel@hamburg.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gibbs@scsiguy.com \
--cc=hahn@coffee.psychology.mcmaster.ca \
--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