public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Lutz Jaenicke <ljaenicke@innominate.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: MPC8313 performance evaluation
Date: Thu, 6 Aug 2009 14:16:55 -0500	[thread overview]
Message-ID: <8731B515-14B1-4580-A196-75E57543C3F9@kernel.crashing.org> (raw)
In-Reply-To: <20090806180035.GA19088@lutz.bln.innominate.local>


On Aug 6, 2009, at 1:00 PM, Lutz Jaenicke wrote:

> Hi!
>
> I am currently evaluating the performance of the MPC8313E for firewall
> (and VPN) purposes.
> The results obtained do not match my expectations so I would be  
> interested
> in some discussion.
>
> Test setup:
> -----------
> A linux 2.6.27 based firewall software is used. The software is the
> same among
> To be replaced: IXP42x custom made board (266MHz and 533MHz)
> * MPC8343 custom made board (400MHz)
> * MPC8313E-RDB Rev. C (333/333)
> As a software firewall the throughput is determined by looking into
> the routing information and IP headers, hence the performance is best
> characterized by "frames/s" which is constant over the frame size
> (as long as no limit is hit like the 100Mbit/s limit on the IXP42x).
>
> With the MPC8343@400MHz I get a throughput of approx. 24500 frames/s
> using the predefined firewall rules.
> With the MPC8313 I get a significantly lower value:
> MPC8313@250MHz          12500fps
> MPC8313@333MHz          14500fps
> MPC8313@416MHz          15500fps      (333MHz type, overclocked)
> Kernel 2.6.27 with SKB recycling from later versions and the
> e300c2/c3/c4 TLB errata workaround. Some pure computational benchmark
> with small footprint (namely "openssl speed") which should fit into
> the cache size indicates the perfect 3/4/5 ratio used.
>
> Some discussion with the the freescale rep. lead to the CSB frequency
> of the 8313 (166MHz) being significantly lower than that of the 8343.
> Is the CSB the critical point here?
> Note: the IXP42x uses an internal bus speed of 133MHz and operates
> at frame rates similar to the 8343...
>
> Does anybody else have numbers for a firewall scenario using 8313
> and/or other processors of the family?
>
> Best regards,
> 	Lutz
> PS: Yes, I know that absolute numbers will be hard to compare with
> other scenarios but relative values would be quite interesting as
> well.

What DDR frequencies (and width) are you running the 8343 vs 8313 at.   
This can have a significant impact on performance.

- k

  reply	other threads:[~2009-08-06 19:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06 18:00 MPC8313 performance evaluation Lutz Jaenicke
2009-08-06 19:16 ` Kumar Gala [this message]
2009-08-07  7:48   ` Lutz Jaenicke
2009-08-07  8:05     ` Liu Dave-R63238
2009-08-07  8:08 ` Liu Dave-R63238
2009-08-07 10:56   ` Lutz Jaenicke
2009-08-07 11:02     ` Lutz Jaenicke

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=8731B515-14B1-4580-A196-75E57543C3F9@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=ljaenicke@innominate.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox