From: Wolfgang Grandegger <wg@grandegger.com>
To: Roman Fietze <roman.fietze@telemotive.de>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: MPC5200B XLB Configuration Issues, FEC RFIFO Events, ATA Crashes
Date: Fri, 18 Dec 2009 09:24:29 +0100 [thread overview]
Message-ID: <4B2B3C3D.4090308@grandegger.com> (raw)
In-Reply-To: <200912161237.09796.roman.fietze@telemotive.de>
Roman Fietze wrote:
> Hello Wolfram,
>
> On Wednesday 09 December 2009 15:57:48 Wolfram Sang wrote:
>
>> Do you have a way to measure performance penalties?
>
> As I said, I do.
>
> And here they are. They won't win a price for the most impartial
> benchmarks ever seen, but thet'll be a good starting point to get a
> feeling what stability might cost.
>
> The board is using the MPC5200B on a board derived from the old
> lite5200, but with the fixes for the MPC5200B. All tests are run using
> an ST940813AM hard drive with an ext2 and an ext3 of 10GB each,
> default mkfs options. The OS is Debian 4.0. The network connection is
> between a fast Athlon XP2 6400 and the target, using 100MBit/s wiring
> and a 100MBit/s switch.
>
> The F always stands for fast settings, coherent cache, XLB features
> like snooping, etc. turned on, XLB config 0x0000a006 or 0x0001a006
> (makes no or no big difference).
>
> The S always stands for slow settings, non coherent cache, XLB
> features like snooping, etc. turned on, XLB config 0x80012006.
What disc access modes, (pio, mwdma or udma) did you use for these tests.
Wolfgang.
next prev parent reply other threads:[~2009-12-18 8:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 14:29 MPC5200B XLB Configuration Issues, FEC RFIFO Events, ATA Crashes Roman Fietze
2009-12-09 14:57 ` Wolfram Sang
2009-12-10 6:09 ` Roman Fietze
2009-12-16 11:37 ` Roman Fietze
2009-12-18 8:24 ` Wolfgang Grandegger [this message]
2009-12-18 9:07 ` Roman Fietze
2010-01-22 20:11 ` Albrecht Dreß
[not found] <1264191106.2224.0-2010-02-02-19-31-49@antares>
2010-02-03 6:16 ` Roman Fietze
2010-02-04 19:35 ` Albrecht Dreß
2010-02-19 18:04 ` Albrecht Dreß
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=4B2B3C3D.4090308@grandegger.com \
--to=wg@grandegger.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=roman.fietze@telemotive.de \
/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.