All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k in wireless-testing won't work in AP mode
Date: Wed, 03 Feb 2010 01:35:40 +0100	[thread overview]
Message-ID: <4B68C4DC.5090607@openwrt.org> (raw)
In-Reply-To: <43e72e891002021627rd07a567v8d739908ee252f56@mail.gmail.com>

On 2010-02-03 1:27 AM, Luis R. Rodriguez wrote:
> On Tue, Feb 2, 2010 at 4:18 PM, Felix Fietkau <nbd@openwrt.org> wrote:
>> On 2010-02-03 1:08 AM, Luis R. Rodriguez wrote:
>>> We have reviewed this. The 64 value came from interoperability
>>> tests against another 802.11n device which had increased delayed BlockAcks
>>> when CTS-to-self was enabled. Although this is a higher value than
>>> what the standard says to use we recommend to just leave the value as-is
>>> and actually use the values from the initvals as the minimum possible
>>> value as those are the values that have been used for a large array
>>> of tests, including WMM interop tests. We cannot gaurantee proper
>>> functionality against other devices otherwise.
>>>
>>> Since the issues so far are obaserved on AR9160 and AR9220
>>> (and not AR9280) and AR9271 (sujith) this might be a bus issue
>>> and the only way to zero in on the issue would be by getting full
>>> register dumps to ensure every other register related to ACK Timeout
>>> is programmed properly (AR_USEC_USEC I think is one) and
>>> taking it from there. Testing different values are welcomed but
>>> upstream we should just use what we have tested with until
>>> we do WMM interop tests with different values and not sure if
>>> we'll be doing that for a while.
>> So how should we handle ACK timeout for different coverage class values?
>> That's my primary concern, since I wrote the patch to support that.
>> Should I just send a patch that adds an offset of 45? (= 64us - 19us,
>> based on the diff between calculated and initval)
> 
> Well so what I meant is that we should ensure hardware is not
> programmed with an ACK/CTS Timeout value lower than what is on the
> initvals already. If changing the coverage class means a different ACK
> timeout is produced we just take the max of the two values.
Taking the max doesn't make any sense to me if this is about working
around delay in the transmission of BlockAcks. Since the coverage class
is meant to compensate delay in the air propagation time, the ACK
timeout should increase along with it, because along with increasing
distance, the worst case delay of the BA of a distant node will get
higher as well.

- Felix

  reply	other threads:[~2010-02-03  0:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-29 23:05 [ath9k-devel] ath9k in wireless-testing won't work in AP mode Pavel Roskin
2010-01-29 23:34 ` Felix Fietkau
2010-01-30 19:39   ` Pavel Roskin
2010-01-30 20:10     ` Felix Fietkau
2010-01-30 20:37       ` Pavel Roskin
2010-01-30 20:46         ` Felix Fietkau
2010-01-30 21:11           ` Pavel Roskin
2010-02-03  0:08           ` Luis R. Rodriguez
2010-02-03  0:18             ` Felix Fietkau
2010-02-03  0:27               ` Luis R. Rodriguez
2010-02-03  0:35                 ` Felix Fietkau [this message]
2010-02-03  0:45                   ` Luis R. Rodriguez
2010-02-03  3:29                     ` Pavel Roskin
2010-02-03 17:16                       ` Luis R. Rodriguez
2010-02-03  4:22             ` Sujith
2010-02-10 10:51             ` Jouni Malinen
2010-02-10 17:33               ` Peter Stuge
2010-02-11  9:12     ` Peter Stuge

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=4B68C4DC.5090607@openwrt.org \
    --to=nbd@openwrt.org \
    --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.