From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: Fabio Estevam <festevam@gmail.com>
Cc: "Jérôme Carretero" <cJ-ko@zougloub.eu>,
"Franky Lin" <franky.lin@broadcom.com>,
"Wright Feng" <Wright.Feng@cypress.com>,
"Arend van Spriel" <arend.vanspriel@broadcom.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: brcmfmac experiment for a specific use case - tx throughput maximization for slow CPU with glomming
Date: Mon, 21 Aug 2017 20:09:42 +0200 [thread overview]
Message-ID: <1503338982.18019.1.camel@embedded.rocks> (raw)
In-Reply-To: <CAOMZO5A1485fcgVRcSKy7QoJnLgoSQerX=MmP_exhsdxOctG6A@mail.gmail.com>
Hi Fabio,
On Fri, 2017-08-18 at 08:50 -0300, Fabio Estevam wrote:
> Hi Jörg,
>
> On Thu, Jun 1, 2017 at 3:37 AM, Jörg Krause <joerg.krause@embedded.rocks> wrote:
>
> > I'm experiencing low throughput with a BCM43362 wifi chip attached via
> > SDIO to an i.MX28 [1,2]. After disabling some Kernel debug features I'm
> > getting now a TCP throughput of 12.5 Mbps for the wifi interface, which
> > is still below the throughput I get for the Cubietruck.
>
> Does it help if you disable CONFIG_PROVE_LOCKING?
No, it does not. I've disabled all settings in "Lock Debugging", but
the TCP throughput is still at ~12.5 Mpbs.
> --- a/arch/arm/configs/mxs_defconfig
> +++ b/arch/arm/configs/mxs_defconfig
> @@ -175,7 +175,6 @@ CONFIG_MAGIC_SYSRQ=y
> CONFIG_DEBUG_KERNEL=y
> CONFIG_LOCKUP_DETECTOR=y
> CONFIG_TIMER_STATS=y
> -CONFIG_PROVE_LOCKING=y
> CONFIG_BLK_DEV_IO_TRACE=y
> CONFIG_STRICT_DEVMEM=y
> CONFIG_DEBUG_USER=y
prev parent reply other threads:[~2017-08-21 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 11:33 brcmfmac experiment for a specific use case - tx throughput maximization for slow CPU with glomming Jérôme Carretero
2017-06-01 6:37 ` Jörg Krause
2017-08-18 11:50 ` Fabio Estevam
2017-08-21 18:09 ` Jörg Krause [this message]
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=1503338982.18019.1.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--cc=Wright.Feng@cypress.com \
--cc=arend.vanspriel@broadcom.com \
--cc=cJ-ko@zougloub.eu \
--cc=festevam@gmail.com \
--cc=franky.lin@broadcom.com \
--cc=linux-wireless@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 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).