From: Kalle Valo <kvalo@codeaurora.org>
To: Gavin Li <gavinli@thegavinli.com>
Cc: arend.vanspriel@broadcom.com, franky.lin@broadcom.com,
hante.meuleman@broadcom.com, linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com, stable@vger.kernel.org,
Gavin Li <git@thegavinli.com>
Subject: Re: [v3] brcmfmac: fix incorrect event channel deduction
Date: Fri, 20 Jan 2017 10:03:14 +0000 (UTC) [thread overview]
Message-ID: <20170120100314.C4AFE609EF@smtp.codeaurora.org> (raw)
In-Reply-To: <20170117232405.7672-1-gavinli@thegavinli.com>
Gavin Li <gavinli@thegavinli.com> wrote:
> From: Gavin Li <git@thegavinli.com>
>
> brcmf_sdio_fromevntchan() was being called on the the data frame
> rather than the software header, causing some frames to be
> mischaracterized as on the event channel rather than the data channel.
>
> This fixes a major performance regression (due to dropped packets). With
> this patch the download speed jumped from 1Mbit/s back up to 40MBit/s due
> to the sheer amount of packets being incorrectly processed.
>
> Fixes: c56caa9db8ab ("brcmfmac: screening firmware event packet")
> Signed-off-by: Gavin Li <git@thegavinli.com>
> Cc: <stable@vger.kernel.org> # 4.7+
> Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com>
> [kvalo@codeaurora.org: improve commit logs based on email discussion]
Patch applied to wireless-drivers-next.git, thanks.
8e290cecdd01 brcmfmac: fix incorrect event channel deduction
--
https://patchwork.kernel.org/patch/9522185/
Documentation about submitting wireless patches and checking status
from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2017-01-20 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 23:24 [PATCH v3] brcmfmac: fix incorrect event channel deduction gavinli
2017-01-18 12:38 ` Arend Van Spriel
2017-01-18 18:39 ` Gavin Li
2017-01-18 22:35 ` Arend Van Spriel
2017-01-19 8:48 ` Kalle Valo
[not found] ` <CA+GxvY6ho89L-Ye7MrbtVM=i+Ck8YSH7JaSG1p=WzH5u_Be0_A@mail.gmail.com>
2017-01-19 8:55 ` Kalle Valo
2017-01-20 10:03 ` Kalle Valo [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=20170120100314.C4AFE609EF@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=gavinli@thegavinli.com \
--cc=git@thegavinli.com \
--cc=hante.meuleman@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.