public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: linux-kernel@vger.kernel.org
Subject: Slower raid sync (pIII_sse) benchmark on AthlonXP
Date: Tue, 2 Sep 2003 11:02:02 -0700	[thread overview]
Message-ID: <20030902180202.GB13684@matchmail.com> (raw)

Are these numbers correct for sse on AthlonXP?  Every time I've seen the
pIII_sse number much closer to pII_mmx...

2.6.0-test4-mm3-1:

raid5: measuring checksumming speed
   8regs     :  2788.000 MB/sec
   8regs_prefetch:  2752.000 MB/sec
   32regs    :  2668.000 MB/sec
   32regs_prefetch:  2252.000 MB/sec
   pIII_sse  :  2792.000 MB/sec
   pII_mmx   :  5556.000 MB/sec
   p5_mmx    :  7360.000 MB/sec
raid5: using function: pIII_sse (2792.000 MB/sec)

processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 6
model		: 8
model name	: AMD Athlon(TM) XP 2600+
stepping	: 1
cpu MHz		: 2083.203
cache size	: 256 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow
bogomips	: 4104.19

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Are these numbers correct for sse on AthlonXP?  Every time I've seen the
pIII_sse number much closer to pII_mmx...

2.6.0-test4-mm3-1:

raid5: measuring checksumming speed
   8regs     :  2788.000 MB/sec
   8regs_prefetch:  2752.000 MB/sec
   32regs    :  2668.000 MB/sec
   32regs_prefetch:  2252.000 MB/sec
   pIII_sse  :  2792.000 MB/sec
   pII_mmx   :  5556.000 MB/sec
   p5_mmx    :  7360.000 MB/sec
raid5: using function: pIII_sse (2792.000 MB/sec)

processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 6
model		: 8
model name	: AMD Athlon(TM) XP 2600+
stepping	: 1
cpu MHz		: 2083.203
cache size	: 256 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow
bogomips	: 4104.19


                 reply	other threads:[~2003-09-02 18:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030902180202.GB13684@matchmail.com \
    --to=mfedyk@matchmail.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