From: mkl@pengutronix.de (Marc Kleine-Budde)
To: linux-arm-kernel@lists.infradead.org
Subject: Some benchmarks on ARM
Date: Mon, 05 Jul 2010 14:45:34 +0200 [thread overview]
Message-ID: <4C31D3EE.7050407@pengutronix.de> (raw)
In-Reply-To: <4C31D30A.9010601@pengutronix.de>
Marc Kleine-Budde wrote:
> Colin Tuckley wrote:
>>> -----Original Message-----
>>> kernel-bounces at lists.infradead.org] On Behalf Of Robert Schwebel
>>> Sent: 02 July 2010 19:03
>>> We have recently made some benchmarks, in order to get a little bit
>>> better fealing about where ARM cpus are today, especially when it comes
>>> to the "recent" ones, and in comparism to the Atom. So we collected a
>>> few benchmarks (most from lmbench) and did some actual measurements.
>> You have the family wrong for (at least) the Cortex-A8, it's a v7. This probably accounts for some of it's slow relative performance since you probably used incorrect compiler switches.
>>
>>> All measurements have been done on 2.6.34.
>> How were the kernels compiled? Was thumb mode used for the ones that support it?
>>
>> You didn't mention the cache state anywhere - it can make a big difference.
>
> After booting all tests are done via ssh, the system was "idle" otherwise.
>
> We're just repeating the tests with "echo 1 > /proc/sys/vm/drop_caches"
> prior to each test.
We'll use "sync; echo 3 > /proc/sys/vm/drop_caches"
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100705/af25163f/attachment.sig>
next prev parent reply other threads:[~2010-07-05 12:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 18:02 Some benchmarks on ARM Robert Schwebel
2010-07-02 20:34 ` Magnus Lilja
2010-07-05 12:24 ` Marc Kleine-Budde
2010-07-05 14:00 ` Russell King - ARM Linux
2010-07-05 15:14 ` Måns Rullgård
2010-07-03 5:44 ` Nicolas Pitre
2010-07-05 13:04 ` Maurus Cuelenaere
2010-07-05 13:23 ` Robert Schwebel
2010-07-05 13:31 ` Mike Rapoport
2010-07-05 13:42 ` Robert Schwebel
2010-07-05 14:15 ` Nicolas Pitre
2010-07-06 5:36 ` Mike Rapoport
2010-07-05 13:53 ` Marek Vasut
2010-07-06 14:02 ` Pavel Machek
2010-07-03 19:48 ` Baruch Siach
2010-07-03 20:08 ` Gilles Chanteperdrix
2010-07-03 20:28 ` Russell King - ARM Linux
2010-07-04 9:47 ` Gilles Chanteperdrix
2010-07-05 8:51 ` Colin Tuckley
2010-07-05 12:29 ` Marc Kleine-Budde
2010-07-05 12:41 ` Marc Kleine-Budde
2010-07-05 12:45 ` Marc Kleine-Budde [this message]
2010-07-29 16:54 ` Robert Schwebel
2010-07-30 10:19 ` Richard Cochran
2010-07-30 11:40 ` Gilles Chanteperdrix
2010-08-19 5:36 ` shiraz hashim
2010-08-19 6:28 ` Robert Schwebel
2010-08-19 7:10 ` shiraz hashim
-- strict thread matches above, loose matches on Subject: below --
2010-07-30 14:47 Tomasz Stanislawski
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=4C31D3EE.7050407@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).