From: Disconnect <lkml@sigkill.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Athlon problem report summary
Date: Fri, 20 Apr 2001 20:30:29 -0400 [thread overview]
Message-ID: <20010420203029.C20176@sigkill.net> (raw)
In-Reply-To: <20010420202235.B20176@sigkill.net> <E14qlGJ-0002b8-00@the-village.bc.nu>
In-Reply-To: <E14qlGJ-0002b8-00@the-village.bc.nu>
On Sat, 21 Apr 2001, Alan Cox did have cause to say:
> K7 optimisation basically enabled the MMX copy/clear code which adds 30-40%
> performance to those functions. It also materially ups the maximum memory
> bandwidth the processor will use which may be where the fun starts.
Not to be slow/dull/etc (I -really- appreciate the help here) but possibly
more stupid questions.
Is there anything out there to test/benchmark MMX ops? (Preferably with
reporting on MMX and equiv non-MMX ops, tunable memory bandwidth, etc.)
Also, I can try that same kernel w/ memory set to HCLK (pc100) instead of
HCLK+33 (pc133). The ram is pc133, but who knows, it might work. (I'm
pretty sure I had it at pc100 before with no change, but not positive.)
---
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1 [www.ebb.org/ungeek]
GIT/CC/CM/AT d--(-)@ s+:-- a-->? C++++$ ULBS*++++$ P+>+++ L++++>+++++
E--- W+++ N+@ o+>$ K? w--->+++++ O- M V-- PS+() PE Y+@ PGP++() t 5---
X-- R tv+@ b++++>$ DI++++ D++(+++) G++ e* h(-)* r++ y++
------END GEEK CODE BLOCK------
next prev parent reply other threads:[~2001-04-21 0:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.fkfenov.14jqeov@ifi.uio.no>
2001-04-16 12:30 ` Athlon problem report summary Alan Cox
2001-04-16 12:33 ` Alan Cox
2001-04-16 13:17 ` Kurt Roeckx
2001-04-20 23:52 ` Disconnect
2001-04-21 0:14 ` Alan Cox
2001-04-21 0:22 ` Disconnect
2001-04-21 0:28 ` Alan Cox
2001-04-21 0:30 ` Disconnect [this message]
2001-04-21 0:34 ` Alan Cox
2001-04-21 9:27 ` Arjan van de Ven
2001-04-21 15:07 ` Disconnect
[not found] ` <fa.fn57bnv.nno4p4@ifi.uio.no>
2001-04-21 2:54 ` Jeff Lightfoot
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=20010420203029.C20176@sigkill.net \
--to=lkml@sigkill.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.