linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
To: linuxwifi <linuxwifi@intel.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"kevin@kevinlocke.name" <kevin@kevinlocke.name>,
	"Coelho, Luciano" <luciano.coelho@intel.com>
Subject: Re: [linuxwifi] [RFC] iwlwifi: enable TX AMPDU for some iwldvm
Date: Tue, 12 Mar 2019 19:47:00 +0000	[thread overview]
Message-ID: <1b6eaef941d3bc887a9fbedea47c2677e5511cdd.camel@intel.com> (raw)
In-Reply-To: <0f9132187a5567fa94e396ed317efbae1aa4de14.camel@intel.com>

On Tue, 2019-03-12 at 21:38 +0200, Luciano Coelho wrote:
> Hi Kevin,
> 
> Johannes (johill) is also in this list. :)
> 
> If this feature was explicitly disabled, it certainly means that
> something was causing problems with it, so I'd be wary to enable it
> for
> all DVM devices.
> 
> I guess we could enable it by default for devices that work fine, but
> we would have to run it in real life for a lot longer with a lot more
> different APs to be sure it won't cause any problems.
> 
> Emmanuel, do you happen to remember what was the issue, so Kevin
> could
> test that specific scenario with this specific NIC?

long long nights of despair.

We had issues with reclaim path upon BACK. This is of course a firmware
problem...

> 
> Kevin, meanwhile you could add the option to your default module
> configuration so it would be used by default on your machine.
> 
> --
> Cheers,
> Luca.
> 
> 
> On Tue, 2019-03-12 at 11:12 -0600, Kevin Locke wrote:
> > Hi Wireless Developers,
> > 
> > I have a Lenovo ThinkPad T430 (2342-CTO) with an Intel Centrino
> > Ultimate-N 6300 (8086:4238) wireless card.  With the help of
> > Reventlov
> > and johill on #linux-wireless, we discovered that enabling TX
> > AMPDU,
> > by passing module option 11n_disable=8 (IWL_ENABLE_HT_TXAGG) to
> > iwlwifi, increased TCP throughput significantly:
> > 
> > With an ASUS RT-ACRH13 AP and `iperf3 -s` running on a server with
> > a
> > 1Gbps wired connection, `iperf3 -R -c` on the ThinkPad increased
> > from
> > 63.2 to 104 Mbits/sec (using MCS 15 40MHz short GI).  With a
> > Buffalo
> > WZR-600DHP running OpenWRT, `iperf3 -R -c` increased from 63.2 to
> > 76.9.
> > 
> > TX AMPDU was disabled by default for all iwldvm cards in
> > 205e2210daa9
> > because "iwldvm don't handle well TX AMPDU".  However, I have been
> > using this configuration for >2 weeks without any issues or
> > measurable
> > change in ping times to the AP.  Are there any other potential
> > side-effects I can check?
> > 
> > Would it be possible to enable TX AMPDU by default for at least
> > some
> > of these cards?  If so, what additional information would be
> > required?
> > 
> > Thanks for considering,
> > Kevin
> > -------------------------------------
> > linuxwifi@eclists.intel.com
> > https://eclists.intel.com/sympa/info/linuxwifi
> > Unsubscribe by sending email to sympa@eclists.intel.com with
> > subject
> > "Unsubscribe linuxwifi"
> 
> 

  reply	other threads:[~2019-03-12 19:47 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 [this message]
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

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=1b6eaef941d3bc887a9fbedea47c2677e5511cdd.camel@intel.com \
    --to=emmanuel.grumbach@intel.com \
    --cc=kevin@kevinlocke.name \
    --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;
as well as URLs for NNTP newsgroup(s).