From: Rob Landley <landley@trommello.org>
To: Larry McVoy <lm@bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: sis630/celeron perf sucks?
Date: Sat, 6 Oct 2001 18:24:18 -0400 [thread overview]
Message-ID: <01100618241801.05593@localhost.localdomain> (raw)
In-Reply-To: <20011006130647.B26223@work.bitmover.com>
In-Reply-To: <20011006130647.B26223@work.bitmover.com>
On Saturday 06 October 2001 16:06, Larry McVoy wrote:
> Has anyone out there seen similar problems with SIS630 motherboards?
> I know that we discussed this recently and people said that the graphics
> chip is eating memory bandwidth but I am not using it, it isn't even in
> SVGA mode, it's in text mode and screen blanked. I also tried setting
> the AGP mem down to 2MB and that made no difference.
>
> The reason I care is that I like these little cheap boxes called "book pcs"
> and the older model was BK810 and used the i810 chipset but the newer ones
> are BK630 and use the SIS630 chipset.
>
> The new ones suck on all the stuff I care about, compiles, BitKeeper
> regressions, just general software dev stuff.
>
> Any insight appreciated.
Run memtest86 to see what your memory bandwidth is.
You can also compare a tight loop ala bogomips with dirtying about as many
pages as you have cache (memtest86 can find this), with dirtying more pages
than you have cache in a big evil loop.
If this shows that your problem ISN'T memory bandwidth, then you'll have
learned something.
> The bummer is that the memory subsystem sucks doggy doo doo on the former.
> Is this a motherboard problem or do the newer celerons suck that bad on
> purpose?
All the celerons I know about have a 66 mhz front side bus speed. (Actually
there was a notebook version with a 100mhz fsb, but no desktop ones I know
of.) It's a totally artificial limitation to get you to buy a real Pentium
III. Intel crippling its low-end to avoid hurting the high end. (They let
AMD do that for them. :)
I've got links bookmarked about this somewhere. You can probably find it on
Tom's Hardware, or check google...
> Check out the bandwidth stuff, the second row should be faster but isn't:
Yup. Blame Intel's marketing department. This isn't a SIS problem, that's
pure Intel's crippling of the DeCeleron...
Rob
next prev parent reply other threads:[~2001-10-08 4:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-06 20:06 sis630/celeron perf sucks? Larry McVoy
2001-10-06 22:24 ` Rob Landley [this message]
2001-10-08 4:40 ` Larry McVoy
2001-10-08 15:58 ` Eric W. Biederman
2001-10-08 19:50 ` Stefan Smietanowski
2001-10-08 20:54 ` Benjamin LaHaise
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=01100618241801.05593@localhost.localdomain \
--to=landley@trommello.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
/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.