On 2012-04-12 16:03, Kevin Hilman wrote:
Gary Thomas<gary@xxxxxxxxxxxx> writes:
On 2012-04-12 12:08, Kevin Hilman wrote:
Gary Thomas<gary@xxxxxxxxxxxx> writes:
On 2012-04-12 10:57, Kevin Hilman wrote:
+Felipe for EHCI question
Gary Thomas<gary@xxxxxxxxxxxx> writes:
[...]
This worked a treat, thanks. My network performance is better
now, but still not what it was. The same TFTP transfer now takes
71 seconds, so about 50% slower than on the 3.0 kernel. Applying the
second [unnamed] patch (arch/arm/mach-omap2/cpuidle34xx.c) made no difference.
And does a CONFIG_PM=n kernel get you back to your v3.0 performance?
Correct.
OK, I just tried your TFTP experiment on a 3530/Overo board with the
same smsc911x NIC that has GPIO interrupts, and I don't see much
difference between a PM-enabled v3.0 and a PM-enabled v3.3.
Are you TFTP'ing the file to an MMC filesystem? Can you try to a
ramdisk[1]? If you're using MMC, it could be MMC driver changes since
v3.0 that are actually causing your performance hit.
I'm testing to a ramdisk, so we're on the same page.
Could you send me your config file so I can compare? Maybe I have something
"dumb" in my settings that aggravates things.
Below is the Kconfig snippet[1] I append to a default
omap2plus_defconfig to enable CPUidle, CPUfreq and some debug. Rebuild
with that appended and these settings override the default ones. I used
omap2plus_defcnfig plus this snippit for v3.0, v3.3 and v3.4-rc2 tests.
Also, what's your performance on 3.4-rc2? The linux-media tree I started
from is a bit post v3.3, so there might be something else causing this.
I just tried with vanilla v3.4-rc2, and I see basically the same
results. Between 35 and 50 seconds for the 24Mb file transfer, which is
similar to the v3.0 and v3.3 results.
Kevin
[1]
CONFIG_CPU_IDLE=y
CONFIG_PM_ADVANCED_DEBUG=y
CONFIG_PM_SLEEP_ADVANCED_DEBUG=y
CONFIG_PM_GENERIC_DOMAINS=y
CONFIG_OMAP_SMARTREFLEX=y
CONFIG_OMAP_SMARTREFLEX_CLASS3=y
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
CONFIG_CPU_FREQ_STAT=y
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_ARM_OMAP2PLUS_CPUFREQ=y
CONFIG_REGULATOR_OMAP_SMPS=y
CONFIG_DEBUG_LL=y
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_USER=y
CONFIG_EARLY_PRINTK=y
CONFIG_DEBUG_SECTION_MISMATCH=y
These settings made no difference.
I just reverified my results to xfer a 39MB file to ramdisk:
3.0 + PM = 39sec
3.3 + PM = 70sec
3.3 - PM = 48sec
so it's not quite the same as 3.0 was, but closer. BTW, your
results normalized to mine would be
3.3 + PM = 56sec
I wish I knew why I'm seeing a big difference between +PM/-PM
and you don't. Is there some way to compare your source tree
(the one you built for v3.3) and mine? I'm not very good with
GIT so I'm not quite sure how to do it.
Sorry for being so much trouble, I'm just in search of all the
performance I can get out of my system :-)
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
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
