From: "John W. Linville" <linville@tuxdriver.com>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ilw@linux.intel.com" <ilw@linux.intel.com>
Subject: Re: pull request: iwlwifi 2014-02-13
Date: Thu, 13 Feb 2014 14:51:36 -0500 [thread overview]
Message-ID: <20140213195136.GI22203@tuxdriver.com> (raw)
In-Reply-To: <52FCC95D.4090609@gmail.com>
On Thu, Feb 13, 2014 at 03:32:13PM +0200, Emmanuel Grumbach wrote:
> Hi John,
>
> One single patch for this pull request for 3.14.
>
> As explicitly written in the commit message, we prefer to disable Tx
> AMPDU on NICs supported by iwldvm. This feature gives a big boost in Tx
> performance, but the firmware is buggy and we can't rely on it.
> Our hope is that most of the users out there want wifi to surf on the
> web which means that they care more for Rx traffic than for Tx.
> People who want to enable it can do so with the help of a module parameter.
>
> Please pull - thanks.
>
> emmanuel
>
>
> The following changes since commit c512865446e6dd5b6e91e81187e75b734ad7cfc7:
>
> iwlwifi: mvm: don't allow A band if SKU forbids it (2014-02-02
> 11:08:42 +0200)
>
> are available in the git repository at:
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes.git
> master
>
> for you to fetch changes up to 205e2210daa975d92ace485a65a31ccc4077fe1a:
>
> iwlwifi: disable TX AMPDU by default for iwldvm (2014-02-13 15:24:35
> +0200)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2014-02-13 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 13:32 pull request: iwlwifi 2014-02-13 Emmanuel Grumbach
2014-02-13 19:51 ` John W. Linville [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=20140213195136.GI22203@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=egrumbach@gmail.com \
--cc=ilw@linux.intel.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).