From: Kyle McMartin <kyle@mcmartin.ca>
To: Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
linux-parisc@vger.kernel.org
Subject: Re: C8000 cpu upgrade problem
Date: Sat, 23 Oct 2010 23:43:15 -0400 [thread overview]
Message-ID: <20101024034314.GQ8332@bombadil.infradead.org> (raw)
In-Reply-To: <alpine.DEB.1.10.1010240432390.30241@artax.karlin.mff.cuni.cz>
On Sun, Oct 24, 2010 at 05:03:25AM +0200, Mikulas Patocka wrote:
> I tried to measure the cache size, sequential memory read showed cutoff at
> 700kB and no cutoff at 32MB. It shows 1.7GB/s below 700kB and 612MB/s
> above. Latency measurements (chasing pointer chain) showed drastic cutoff
> at 700kB (from 3ns to 300ns) and no cutoff at 32MB.
>
> It may be that the lack of L2 cache is the reason why the CPUs don't
> support multiprocessing ... I may buy two better CPUs, if I had actually
> guarantee that the machine isn't locked (I don't want to waste more money
> just to find out that the firmware lock doesn't go away).
>
FWIW, I'd recommend running in non-SMP mode on pa8800/8900 anyway, as
our cache flushing is a bit... suboptimal right now (doing whole cache
flushes on fork and such.) Which, coupled with the gigantic caches on
those cpus which must be flushed just tanks performance.
I've been working on cleaning up jejb's patchset from back in the
bitkeeper days to properly do deferred flushing, but time is constantly
against me (sigh, I don't think I've even powered on my C8000 in a few
years now... explains why I didn't catch your e1000 issue there. :)
--Kyle
next prev parent reply other threads:[~2010-10-24 3:43 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101024020337.725094D30@hiauly1.hia.nrc.ca>
2010-10-24 3:03 ` C8000 cpu upgrade problem Mikulas Patocka
2010-10-24 3:43 ` Kyle McMartin [this message]
2010-10-26 2:16 ` PA caches (was: C8000 cpu upgrade problem) Mikulas Patocka
2010-10-26 3:04 ` Kyle McMartin
2010-10-26 4:30 ` John David Anglin
2010-10-26 16:02 ` Mikulas Patocka
2010-10-27 1:29 ` John David Anglin
2010-10-27 2:40 ` John David Anglin
2010-10-27 4:50 ` James Bottomley
2010-10-27 8:06 ` Mikulas Patocka
2010-10-27 8:35 ` Mikulas Patocka
2010-10-27 14:18 ` James Bottomley
2010-10-27 14:07 ` James Bottomley
2010-10-27 16:28 ` Mikulas Patocka
2010-10-27 16:35 ` James Bottomley
2010-10-27 16:50 ` Mikulas Patocka
2010-10-27 17:07 ` James Bottomley
2010-10-28 6:04 ` John David Anglin
2010-10-28 16:55 ` James Bottomley
2010-10-27 9:04 ` sym53c8xx_2 data corruption Mikulas Patocka
2010-10-27 14:46 ` James Bottomley
2010-10-27 16:19 ` Mikulas Patocka
2010-10-27 16:37 ` James Bottomley
2010-10-28 5:59 ` Grant Grundler
2010-12-18 20:13 ` PA caches (was: C8000 cpu upgrade problem) John David Anglin
2010-10-24 4:01 ` C8000 cpu upgrade problem John David Anglin
2010-10-26 2:04 ` Mikulas Patocka
2010-10-22 14:07 Mikulas Patocka
2010-10-22 18:09 ` Carlos O'Donell
2010-10-23 9:21 ` Mikulas Patocka
2010-10-23 11:22 ` Carlos O'Donell
2010-10-23 15:25 ` Matt Turner
2010-10-23 16:40 ` Mikulas Patocka
2010-10-23 15:47 ` John David Anglin
2010-10-23 16:02 ` Mikulas Patocka
2010-10-23 17:41 ` John David Anglin
2010-10-23 17:53 ` Mikulas Patocka
2010-10-23 18:11 ` John David Anglin
2010-10-23 18:33 ` Mikulas Patocka
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=20101024034314.GQ8332@bombadil.infradead.org \
--to=kyle@mcmartin.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=linux-parisc@vger.kernel.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
/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