Can you dump the first few lines of the kernel log_buf during the kernel boot? Something like this: [ 0.000000] Linux version 2.6.29-omap1-00005-gf9f407c-dirty (romit@maxwell) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #14 PREEMPT Fri Oct 9 14:04:52 IST 2009 [ 0.000000] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387f [ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache [ 0.000000] Machine: OMAP ZOOM2 board [ 0.000000] Memory policy: ECC disabled, Data cache writeback [ 0.000000] L2 CACHE is enabled in bootloader [ 0.000000] OMAP3430 ES3.1 It should tell you if L2 cache is enabled or not. Thanks, -Romit >-----Original Message----- >From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- >owner@xxxxxxxxxxxxxxx] On Behalf Of epsi@xxxxxx >Sent: Monday, October 12, 2009 1:24 PM >To: linux-omap@xxxxxxxxxxxxxxx >Subject: Memory performance / Cache problem > >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@xxxxxxxxxxxxxxx >More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
