linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Felix Fietkau <nbd@openwrt.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: brcmsmac: regression in transmit throughput since 3.19-rc1
Date: Mon, 19 Jan 2015 16:48:03 +0100	[thread overview]
Message-ID: <54BD2733.6090305@broadcom.com> (raw)
In-Reply-To: <1421671947.1965.27.camel@sipsolutions.net>

On 01/19/15 13:52, Johannes Berg wrote:
> Hi Arend,
>
>> On our nightly test setups I found that STA->AP TCP iperf showed a
>> regression in brcmsmac after I upgraded them from 3.18-rc5
>> wireless-testing (f638577)to 3.19-rc1 wireless-testing (f9e7c6c). The
>> attached pictures are historic results showing clear drop on the last run.
>>
>> Has there been any report on there since 3.19-rc1 and would you have a
>> pointer on where to start looking. The changes in brcmsmac look trivial
>> so looking at mac80211 now. There are some changes in minstrel and
>> brcmsmac is using minstrel_ht rate control.
>
> I haven't heard of anything like that yet. No idea where to look either
> - but the drop is significant enough that perhaps you can bisect?

Bisect it is. Was hoping for some obvious change to avoid that.

Regards,
Arend

      reply	other threads:[~2015-01-19 15:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-18 13:26 brcmsmac: regression in transmit throughput since 3.19-rc1 Arend van Spriel
2015-01-19 12:52 ` Johannes Berg
2015-01-19 15:48   ` Arend van Spriel [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=54BD2733.6090305@broadcom.com \
    --to=arend@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@openwrt.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).