public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Craig Whitmore" <linuxkernel@orcon.net.nz>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
	"Dave Jones" <davej@codemonkey.org.uk>
Cc: "Martin Knoblauch" <knobi@knobisoft.de>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Memory performance on Serverworks GC-LE based system poor?
Date: Mon, 11 Nov 2002 14:22:39 +1300	[thread overview]
Message-ID: <055901c28920$d33d8ba0$6df058db@PC2> (raw)
In-Reply-To: 1036978410.2919.16.camel@irongate.swansea.linux.org.uk

I get 1600 on a similar machine but with a Intel SHG2 motherboard
(ServerWorks GC LE Chipset as well) (Same RAM + Processors)
Maybe not a very good Motherboard you have?

Thanks
Craig

> >
> >  >  I have experienced extreme low STREAMS numbers (about 600 MB/sec for
Triad)
> >  > on two dual CPU systems based on the ServerWorks GC-LE chipset
(SuperMicro
> >  > P4DLR+ mainboard). Both systems had 2x2.4 GHz XEONs, 4GB of DDR
memory and
> >  > were running kernel 2.4.18. I would usually expect STREAMS numbers of
about
> >  > 2000 MB/sec for this kind of systems.
> >  >
> >  > Does this ring any bells?
> >
> > ISTR serverworks LE errata with MTRRs and write-combining.
> > Whether this is biting you or not I can't say.
>
> Write combining would really only bite graphics cards. The only other
> performance errata I know about affects the CIOB20 earlier revisions
> (vendor serverworks id 0x0006)


  reply	other threads:[~2002-11-11  1:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-11  0:30 Memory performance on Serverworks GC-LE based system poor? Martin Knoblauch
2002-11-11  0:51 ` Dave Jones
2002-11-11  1:33   ` Alan Cox
2002-11-11  1:22     ` Craig Whitmore [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-11  1:37 Manish Lachwani
2002-11-11  1:39 Manish Lachwani
2002-11-11  9:47 Martin Knoblauch
2002-11-11 12:04 Martin Knoblauch
2002-11-12 18:42 Martin Knoblauch

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='055901c28920$d33d8ba0$6df058db@PC2' \
    --to=linuxkernel@orcon.net.nz \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davej@codemonkey.org.uk \
    --cc=knobi@knobisoft.de \
    --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