All of lore.kernel.org
 help / color / mirror / Atom feed
From: epsi@gmx.de
To: linux-omap@vger.kernel.org
Subject: Memory performance  / Cache problem
Date: Mon, 12 Oct 2009 09:54:09 +0200	[thread overview]
Message-ID: <20091012075409.186580@gmx.net> (raw)

I found the memory performance of newer kernels are quit poor on an EVM-Omap3 board. It works with 2-6 times performance on the old 2.6.22 kernel from TI's PSP.

Possible reasons:
- problem in config the kernel (did omap3_evm_defconfig)
- problem in kernel
- kernel expects some settings from uboot, which are not done there

I have tried the 2.6.29rc3 (from TI's PSP) and the 2.6.31 from git-tree.
Both behave quite simular:

Transport in MByte:
  memcpy =   204.073, loop4 =   183.212, loop1 =    81.693, rand =
4.534

while the 22 kernel:
 memcpy =   453.932, loop4 =   469.934, loop1 =   125.031, rand =
29.631

Can someone give me help or can at least confirm that?
Best regards
Steffen
-- 
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2009-10-12  7:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12  7:54 epsi [this message]
2009-10-12  8:09 ` Memory performance / Cache problem Dasgupta, Romit
2009-10-12  8:35 ` Siarhei Siamashka
2009-10-13  9:13   ` epsi
  -- strict thread matches above, loose matches on Subject: below --
2009-10-12  8:38 epsi
2009-10-12  9:07 ` Dasgupta, Romit
2009-10-12  9:51   ` Dasgupta, Romit
2009-10-12  9:12 ` Premi, Sanjeev
2009-10-14 13:59 ` Woodruff, Richard
2009-10-14 14:48   ` epsi
2009-10-14 17:37     ` Siarhei Siamashka
2009-10-14 17:46       ` Woodruff, Richard
2009-10-15 10:20       ` epsi

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=20091012075409.186580@gmx.net \
    --to=epsi@gmx.de \
    --cc=linux-omap@vger.kernel.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 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.