public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "freaky" <freaky@bananateam.nl>
To: <korn-linuxkernel@chardonnay.math.bme.hu>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.4 very slow memory access on abit kd7raid (kt400); ten times slower than on kg7raid
Date: Sun, 27 Oct 2002 08:39:10 +0100	[thread overview]
Message-ID: <006001c27d8b$f0a75720$1400a8c0@Freaky> (raw)
In-Reply-To: 20021027032811.GM27554@nilus-2690.adsl.datanet.hu

l> Everything slowed down. The easiest way to demontsrate this is by looking
at
> these figures:
>
>  raid5: measuring checksumming speed
> -   8regs     :  2343.600 MB/sec
> -   32regs    :  1944.000 MB/sec
> -   pIII_sse  :  4163.600 MB/sec
> -   pII_mmx   :  3584.400 MB/sec
> -   p5_mmx    :  4600.800 MB/sec
> -raid5: using function: pIII_sse (4163.600 MB/sec)
> +   8regs     :   228.400 MB/sec
> +   32regs    :   199.200 MB/sec
> +   pIII_sse  :   352.000 MB/sec
> +   pII_mmx   :   316.800 MB/sec
> +   p5_mmx    :   432.800 MB/sec
> +raid5: using function: pIII_sse (352.000 MB/sec)
>
> Old motherboard above, new below. (Why it chose pIII_sse even when p5_mmx
> was faster is also an interesting question... :)

I have seen the same on a precompiled slackware 8.1 raid.s kernel I tried
for my promise controller. It's an AMD AthlonXP 2000+. Like you I found that
the PIII_SSE was slower than the P5_MMX and still got selected. I got higher
numers than you though, around your old mobo's speeds.... (KT333 chipset).
(MSI KT3 Ultra2-R). specs are in the KT333, IO-APIC, Promise Fasttak, Initrd
topic.


the 5 disks spanning ram image doesn't even load properly with me, maybe
it's caused by memory problems as well? Tho' I thought north bridges are for
memory access whilst I only get a message that my southbridge isn't
recognized...




  reply	other threads:[~2002-10-27  7:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-27  3:28 2.4 very slow memory access on abit kd7raid (kt400); ten times slower than on kg7raid KORN Andras
2002-10-27  7:39 ` freaky [this message]
     [not found] ` <20021027075346.GB29184@alpha.home.local>
     [not found]   ` <Pine.LNX.4.33.0210270139530.22820-100000@coffee.psychology.mcmaster.ca>
2002-10-27 13:33     ` KORN Andras
     [not found] ` <Pine.LNX.4.44.0210271245430.3202-100000@pianoman.cluster.toy>
2002-10-27 18:19   ` [solved] " KORN Andras
2002-10-28  1:42     ` John Clemens
  -- strict thread matches above, loose matches on Subject: below --
2002-10-27  9:16 Manfred Spraul

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='006001c27d8b$f0a75720$1400a8c0@Freaky' \
    --to=freaky@bananateam.nl \
    --cc=korn-linuxkernel@chardonnay.math.bme.hu \
    --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