All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul Stoaks" <paul@foresight-mands.com>
To: "'Georgiewskiy Yuriy'" <bottleman@icf.org.ru>,
	"'Chaoxing Lin'" <Chaoxing.Lin@ultra-3eti.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: RE: help: 802.11s bad performance with 802.11n enabled
Date: Mon, 3 Dec 2012 10:21:56 -0800	[thread overview]
Message-ID: <005601cdd183$14666bf0$3d3343d0$@com> (raw)
In-Reply-To: <alpine.DEB.2.02.1212031938250.7349@icf.org.ru>

What kind of traffic are you pushing through (packet sizes?)  Are they fixed
size, fixed rate, or ...?

Paul


-----Original Message-----
From: linux-wireless-owner@vger.kernel.org
[mailto:linux-wireless-owner@vger.kernel.org] On Behalf Of Georgiewskiy
Yuriy
Sent: Monday, December 03, 2012 7:44 AM
To: Chaoxing Lin
Cc: linux-wireless@vger.kernel.org
Subject: RE: help: 802.11s bad performance with 802.11n enabled

On 2012-12-03 14:56 -0000, Chaoxing Lin wrote Georgiewskiy Yuriy:

CL>CL>For experiment, I changed ath9k driver to disable 802.11n packet
aggregation. The network becomes much better.
CL>CL>It's as stable as running 802.11a only mode.
CL>CL>So it seems that the aggregation plays a big role in in-stability of
802.11s network with 802.11n.
CL>CL>Any one has any idea why?
CL>
CL>Can you post a patch? i want test this too.
CL>
CL>The change is easy
CL>In ath9k/init.c
CL>Function ath9k_set_hw_capab()
CL>Replace below
CL>    if (sc->sc_ah->caps.hw_caps & ATH9K_HW_CAP_HT)
CL>         hw->flags |= IEEE80211_HW_AMPDU_AGGREGATION; with
CL>	hw->flags &= ~IEEE80211_HW_AMPDU_AGGREGATION;

On first look in my case disabled aggregation reduces packet loss, link is
more reliable, but it's also drop throughput to 15-20 Mbits/sec from about
~50 with aggregation enabled.

C уважением                       With Best Regards
Георгиевский Юрий.                Georgiewskiy Yuriy
+7 4872 711666                    +7 4872 711666
факс +7 4872 711143               fax +7 4872 711143
Компания ООО "Ай Ти Сервис"       IT Service Ltd
http://nkoort.ru                  http://nkoort.ru
JID: GHhost@icf.org.ru            JID: GHhost@icf.org.ru
YG129-RIPE                        YG129-RIPE


  parent reply	other threads:[~2012-12-03 18:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-03 14:37 help: 802.11s bad performance with 802.11n enabled Chaoxing Lin
2012-12-03 14:45 ` Georgiewskiy Yuriy
2012-12-03 14:56   ` Chaoxing Lin
2012-12-03 15:43     ` Georgiewskiy Yuriy
2012-12-03 15:47       ` Chaoxing Lin
2012-12-03 18:21       ` Paul Stoaks [this message]
2012-12-03 18:33         ` Georgiewskiy Yuriy
2012-12-03 19:02         ` Chaoxing Lin
2012-12-08  3:17   ` Thomas Pedersen
2012-12-08  3:23     ` Georgiewskiy Yuriy
2012-12-08  3:29       ` Georgiewskiy Yuriy
2012-12-08  3:37         ` Thomas Pedersen
2012-12-08  3:47           ` Georgiewskiy Yuriy
2012-12-10 15:48             ` Chaoxing Lin
2012-12-10 19:13               ` Thomas Pedersen
2012-12-10 19:28                 ` Chaoxing Lin
2013-01-17 16:14                 ` Chaoxing Lin
2012-12-08  3:37       ` Thomas Pedersen
2012-12-10 15:23     ` Chaoxing Lin
2012-12-10 15:11   ` Chaoxing Lin
2012-12-04  4:35 ` Thomas Pedersen
2012-12-04  8:03   ` Adrian Chadd
  -- strict thread matches above, loose matches on Subject: below --
2012-12-03 16:33 Chaoxing Lin
2012-11-17  9:20 Yeoh Chun-Yeow
2012-11-16 17:41 Chaoxing Lin

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='005601cdd183$14666bf0$3d3343d0$@com' \
    --to=paul@foresight-mands.com \
    --cc=Chaoxing.Lin@ultra-3eti.com \
    --cc=bottleman@icf.org.ru \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.