From: Jouni Malinen <jouni.malinen@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] WMM settings and AP performance
Date: Tue, 26 May 2009 21:22:47 +0300 [thread overview]
Message-ID: <1243362167.2923.17.camel@jm-desktop> (raw)
In-Reply-To: <1243361510.2923.10.camel@jm-desktop>
On Tue, 2009-05-26 at 11:11 -0700, Jouni Malinen wrote:
> On Tue, 2009-05-26 at 10:46 -0700, Luis Rodriguez wrote:
> > On Mon, May 25, 2009 at 06:52:41PM -0700, Jeff Hansen wrote:
> That 25/30 Mbps to 2 Mbps is quite a huge difference and in order for
> QoS parameters to cause something like this, they would need to be
> seriously wrong..
And well, it turns out that the values are indeed seriously wrong.. cw
min and max values are swapped by
b4af0b7ffa5f448bd12f81d2539ee2155919d493.
Jeff: if you have a chance, you could try swapping the cw_max = aCWmin
and cw_min = aCWmax value to actually set cw_max = aCWmax and cw_min =
aCWmin.. In addition to this, I would actually recommend adding the
explicit tx_queue_data* parameters into hostapd.conf even if you are not
using WMM. This should work around the current bug and it will also set
the parameters in a way which are more suitable for an AP (the defaults
set in mac80211 are for station mode). In other words, add following
into hostapd.conf:
tx_queue_data3_aifs=7
tx_queue_data3_cwmin=15
tx_queue_data3_cwmax=1023
tx_queue_data3_burst=0
tx_queue_data2_aifs=3
tx_queue_data2_cwmin=15
tx_queue_data2_cwmax=63
tx_queue_data2_burst=0
tx_queue_data1_aifs=1
tx_queue_data1_cwmin=7
tx_queue_data1_cwmax=15
tx_queue_data1_burst=3.0
tx_queue_data0_aifs=1
tx_queue_data0_cwmin=3
tx_queue_data0_cwmax=7
tx_queue_data0_burst=1.5
- Jouni
WARNING: multiple messages have this Message-ID (diff)
From: Jouni Malinen <jouni.malinen@atheros.com>
To: Luis Rodriguez <Luis.Rodriguez@Atheros.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Jeff Hansen <x@jeffhansen.com>
Subject: Re: [ath9k-devel] WMM settings and AP performance
Date: Tue, 26 May 2009 21:22:47 +0300 [thread overview]
Message-ID: <1243362167.2923.17.camel@jm-desktop> (raw)
In-Reply-To: <1243361510.2923.10.camel@jm-desktop>
On Tue, 2009-05-26 at 11:11 -0700, Jouni Malinen wrote:
> On Tue, 2009-05-26 at 10:46 -0700, Luis Rodriguez wrote:
> > On Mon, May 25, 2009 at 06:52:41PM -0700, Jeff Hansen wrote:
> That 25/30 Mbps to 2 Mbps is quite a huge difference and in order for
> QoS parameters to cause something like this, they would need to be
> seriously wrong..
And well, it turns out that the values are indeed seriously wrong.. cw
min and max values are swapped by
b4af0b7ffa5f448bd12f81d2539ee2155919d493.
Jeff: if you have a chance, you could try swapping the cw_max = aCWmin
and cw_min = aCWmax value to actually set cw_max = aCWmax and cw_min =
aCWmin.. In addition to this, I would actually recommend adding the
explicit tx_queue_data* parameters into hostapd.conf even if you are not
using WMM. This should work around the current bug and it will also set
the parameters in a way which are more suitable for an AP (the defaults
set in mac80211 are for station mode). In other words, add following
into hostapd.conf:
tx_queue_data3_aifs=7
tx_queue_data3_cwmin=15
tx_queue_data3_cwmax=1023
tx_queue_data3_burst=0
tx_queue_data2_aifs=3
tx_queue_data2_cwmin=15
tx_queue_data2_cwmax=63
tx_queue_data2_burst=0
tx_queue_data1_aifs=1
tx_queue_data1_cwmin=7
tx_queue_data1_cwmax=15
tx_queue_data1_burst=3.0
tx_queue_data0_aifs=1
tx_queue_data0_cwmin=3
tx_queue_data0_cwmax=7
tx_queue_data0_burst=1.5
- Jouni
next prev parent reply other threads:[~2009-05-26 18:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 1:52 [ath9k-devel] WMM settings and AP performance Jeff Hansen
2009-05-26 17:46 ` Luis R. Rodriguez
2009-05-26 17:46 ` Luis R. Rodriguez
2009-05-26 18:11 ` Jouni Malinen
2009-05-26 18:11 ` Jouni Malinen
2009-05-26 18:22 ` Jouni Malinen [this message]
2009-05-26 18:22 ` Jouni Malinen
2009-05-26 18:27 ` Jeff Hansen
2009-05-27 4:27 ` Jeff Hansen
2009-05-27 4:27 ` Jeff Hansen
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=1243362167.2923.17.camel@jm-desktop \
--to=jouni.malinen@atheros.com \
--cc=ath9k-devel@lists.ath9k.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.