From: Emmanuel Grumbach <egrumbach@gmail.com>
To: Julian Sikorski <belegdol@gmail.com>, unlisted-recipients:;
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Low 5 GHz performance of Intel Advanced-N 6230
Date: Sat, 26 Apr 2014 20:28:57 +0300 [thread overview]
Message-ID: <535BECD9.1070103@gmail.com> (raw)
In-Reply-To: <535AE15D.8010704@gmail.com>
On 04/26/2014 01:27 AM, Julian Sikorski wrote:
> W dniu 25.04.2014 11:51, Emmanuel Grumbach pisze:
>>
>>
>> On 04/25/2014 12:15 PM, Rafał Miłecki wrote:
>>> 2014-04-25 9:46 GMT+02:00 Emmanuel Grumbach <egrumbach@gmail.com>:
>>>> On 04/24/2014 07:24 PM, Julian Sikorski wrote:
>>>>> Is such a major performance hit expected from this change? Here is the
>>>>> commit in question:
>>>>> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-3.13.y&id=45e5cb4f43d33e72ff5f98c80b081eb42e4e4182
>>>>>
>>>>
>>>> Right - I disabled TX APMDU in this patch. This feature gives a big boost in TX performance, but lots of people experienced bugs that disappeared when this feature was disabled. This bug is in the firmware. Since the most common use case is to browse the internet which is more Rx than Tx, I decided to disabled this feature by default and allow people to enabled it using the module parameter.
>>>
>>> Any plans to update (fix) the firmware?
>>>
>>
>> I don't work on the firmware level, so I can't really say, but I doubt someone will have the cycles to fix the firmware for these devices. Newer devices (7260 and up) have this feature enabled.
>>
> Can this feature be disabled on a per-device basis? It clearly works for
> 6230 and is a huge performance hit when gone.
>
It works for you - but for others it didn't.
prev parent reply other threads:[~2014-04-26 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 6:10 Low 5 GHz performance of Intel Advanced-N 6230 Julian Sikorski
2014-04-24 16:24 ` Julian Sikorski
2014-04-25 7:46 ` Emmanuel Grumbach
2014-04-25 9:15 ` Rafał Miłecki
2014-04-25 9:51 ` Emmanuel Grumbach
2014-04-25 22:27 ` Julian Sikorski
2014-04-26 17:28 ` Emmanuel Grumbach [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=535BECD9.1070103@gmail.com \
--to=egrumbach@gmail.com \
--cc=belegdol@gmail.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).