From: "John W. Linville" <linville@tuxdriver.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Intel Linux Wireless <ilw@linux.intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
Subject: Re: [PATCH v2] iwlagn: use cts-to-self protection on 5000 adapters series
Date: Mon, 6 Jun 2011 14:21:48 -0400 [thread overview]
Message-ID: <20110606182147.GE2604@tuxdriver.com> (raw)
In-Reply-To: <20110606085851.GA2391@redhat.com>
On Mon, Jun 06, 2011 at 10:58:52AM +0200, Stanislaw Gruszka wrote:
> On Thu, May 26, 2011 at 07:50:42AM -0700, Guy, Wey-Yi wrote:
> > On Thu, 2011-05-26 at 08:14 -0700, Stanislaw Gruszka wrote:
> > > This patch fixes 802.11n stability and performance regression we have
> > > since 2.6.35. It boost performance on my 5GHz N-only network from about
> > > 5MB/s to 8MB/s. Similar percentage boost can be observed on 2.4 GHz.
> > >
> > > These are test results of 5x downloading of approximately 700MB iso
> > > image:
> > >
> > > vanilla: 5.27 5.22 4.94 4.47 5.31 ; avr 5.0420 std 0.35110
> > > patched: 8.07 7.95 8.06 7.99 7.96 ; avr 8.0060 std 0.055946
> > >
> > > This was achieved with NetworkManager configured to do not perform
> > > periodical scans, by configuring constant BSSID. With periodical scans,
> > > after some time, performance downgrade to unpatched driver level, like
> > > in example below:
> > >
> > > patched: 7.40 7.61 4.28 4.37 4.80 avr 5.6920 std 1.6683
> > >
> > > However patch still make better here, since similar test on unpatched
> > > driver make link disconnects with below messages after some time:
> > >
> > > wlan1: authenticate with 00:23:69:35:d1:3f (try 1)
> > > wlan1: authenticate with 00:23:69:35:d1:3f (try 2)
> > > wlan1: authenticate with 00:23:69:35:d1:3f (try 3)
> > > wlan1: authentication with 00:23:69:35:d1:3f timed out
> > >
> > > On 2.6.35 kernel patch helps against connection hangs with messages:
> > >
> > > iwlagn 0000:20:00.0: queue 10 stuck 3 time. Fw reload.
> > > iwlagn 0000:20:00.0: On demand firmware reload
> > > iwlagn 0000:20:00.0: Stopping AGG while state not ON or starting
> > >
> > > Cc: stable@kernel.org # 2.6.35+
> > > Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
> > Acked-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
>
> John, can you apply that patch and push upstream? Or should I
> repost? I want backport it to Fedora 2.6.35 as it fixes random
> 11n connection hangs there (common F-14 bug).
Sorry, I was waiting to see if Daniel was going to reply further...
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-06-06 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 15:14 [PATCH v2] iwlagn: use cts-to-self protection on 5000 adapters series Stanislaw Gruszka
2011-05-26 14:50 ` Guy, Wey-Yi
2011-05-26 15:20 ` Daniel Halperin
2011-05-30 9:40 ` Stanislaw Gruszka
2011-06-06 8:58 ` Stanislaw Gruszka
2011-06-06 18:21 ` John W. Linville [this message]
2011-06-06 21:35 ` Daniel Halperin
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=20110606182147.GE2604@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ilw@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=sgruszka@redhat.com \
--cc=wey-yi.w.guy@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).