mmc: core: complete/wait_for_completion performance
Jörg Krause
joerg.krause at embedded.rocks
Sun Nov 20 06:42:09 PST 2016
Hi Stefan,
On Sun, 2016-11-20 at 14:28 +0100, Stefan Wahren wrote:
> Hi Jörg,
>
> > Jörg Krause <joerg.krause at embedded.rocks> hat am 20. November 2016
> > um 13:27
> > geschrieben:
> >
> >
> > Hi,
> >
> > I started the discussion on this mailing list in another thread
> > [1],
> > but I'd like to move it to a new thread, because it might be mmc
> > specific.
> >
> > The issue is that I am noticed low wifi network throughput on an
> > i.MX28
> > board with the mainline kernel (v4.7.10, about 6 Mbps) compared to
> > the
> > vendor kernel (Freescale v2.6.35.3, about 20 Mbps). The wifi chip
> > is
> > attached using the SDIO interface.
> >
> > I started investigation where the bottleneck in the mainline
> > kernel might come from. Therefore I checked that the configs and
> > settings for the interfaces and drivers are the same. They are.
>
> so you're not using the mxs_defconfig settings anymore?
No, I changed the settings.
> Better provide your settings because there are differences between
> the vendor defconfig and mainline defconfig.
The configs I have for the vendor and mainline kernel are pretty much
the same for the parts you showed as an example:
Vendor kernel config:
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_PREEMPT=y
CONFIG_HZ=100
CONFIG_DEFAULT_IOSCHED="cfq"
Mainline kernel config:
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ_COMMON=y
CONFIG_NO_HZ_IDLE=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_PREEMPT=y
CONFIG_HZ=100
CONFIG_DEFAULT_IOSCHED="cfq"
Jörg
More information about the linux-arm-kernel
mailing list