From: Kevin Locke <kevin@kevinlocke.name>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
Cc: linuxwifi@intel.com, linux-wireless@vger.kernel.org, "Coelho,
Luciano" <luciano.coelho@intel.com>
Subject: Re: [linuxwifi] [RFC] iwlwifi: enable TX AMPDU for some iwldvm
Date: Wed, 13 Mar 2019 09:06:34 -0600 [thread overview]
Message-ID: <20190313150634.GA10043@kevinolos> (raw)
In-Reply-To: <cdd094bd29f1e20dc5577fcbad6a7b404e66407a.camel@intel.com>
On Wed, 2019-03-13 at 04:58 +0000, Grumbach, Emmanuel wrote:
> Just to align on expectations, I don't feel like enable A-MPDU by
> default regardless of what will come out of this. People stopped
> complaining after we disabled A-MPDU and the very very very few people
> that did need more throughput knew how to enable them with the module
> parameter. So, I don't plan to re-enable A-MPDU by default.
I understand. I disagree that very few people would benefit from
nearly doubling TCP throughput or that the fix is known/obvious.
However, if it's not worth the risk and/or effort, or there is no
reliable way to determine which devices/configurations are unaffected,
so be it. Resources are limited and that's totally understandable.
Let me know if there is anything else I can do to assist.
Thanks,
Kevin
prev parent reply other threads:[~2019-03-13 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 17:12 [RFC] iwlwifi: enable TX AMPDU for some iwldvm Kevin Locke
2019-03-12 19:38 ` [linuxwifi] " Luciano Coelho
2019-03-12 19:47 ` Grumbach, Emmanuel
2019-03-12 20:31 ` Kevin Locke
2019-03-12 20:48 ` Grumbach, Emmanuel
2019-03-12 21:44 ` Kevin Locke
2019-03-13 4:58 ` Grumbach, Emmanuel
2019-03-13 15:06 ` Kevin Locke [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=20190313150634.GA10043@kevinolos \
--to=kevin@kevinlocke.name \
--cc=emmanuel.grumbach@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luciano.coelho@intel.com \
/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