From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: "Jérôme Carretero" <cJ-ko@zougloub.eu>,
"Franky Lin" <franky.lin@broadcom.com>,
"Wright Feng" <Wright.Feng@cypress.com>
Cc: Arend van Spriel <arend.vanspriel@broadcom.com>,
linux-wireless@vger.kernel.org
Subject: Re: brcmfmac experiment for a specific use case - tx throughput maximization for slow CPU with glomming
Date: Thu, 01 Jun 2017 08:37:54 +0200 [thread overview]
Message-ID: <1496299074.13131.3.camel@embedded.rocks> (raw)
In-Reply-To: <20170524073326.3a16481b@Vantage>
Hi Jérôme,
On Wed, 2017-05-24 at 07:33 -0400, Jérôme Carretero wrote:
> Hi,
>
>
> I've crippled a Raspberry Pi 3 (1 core, 200 MHz) and observed that the
> glomming feature has a definite impact on TX performance, but it looks
> like at this CPU frequency, the work queue is solicited "too often"
> by brcmf_sdio_trigger_dpc() and glomming is only doing 4 packets at
> once, resulting in maybe a sub-optimal throughput.
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.
>
> I have a vague idea that deliberately delaying the transmissions so as
> to wait for either a small timeout, or the glomming level has been
> reached, would be something worth exploring.
> But I haven't spent a long time looking at the driver.
If you are in need for any testing I'm willing to help!
[1] https://www.spinics.net/lists/linux-wireless/msg153257.html
[2] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-October/
461137.html
Jörg
next prev parent reply other threads:[~2017-06-01 6:47 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 [this message]
2017-08-18 11:50 ` Fabio Estevam
2017-08-21 18:09 ` Jörg Krause
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=1496299074.13131.3.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--cc=Wright.Feng@cypress.com \
--cc=arend.vanspriel@broadcom.com \
--cc=cJ-ko@zougloub.eu \
--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).