All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Guerin <jonathan@guerin.id.au>
To: linux-wireless <linux-wireless@vger.kernel.org>,
	ath5k-devel <ath5k-devel@lists.ath5k.org>
Subject: Re: [support] ath5k contention windows
Date: Tue, 14 Sep 2010 15:53:06 +1000	[thread overview]
Message-ID: <AANLkTikvdkR=w-vGL=0LHnxQSibfoFBpuhLwjJZWVCuM@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=azJS6bn7-=Bbb--ibACaQWqv4ZGLMUpfxynm7@mail.gmail.com>

Hi all,

I have some behaviour I'm observing with some Atheros cards we use
that doesn't seem to match what the initvals of ath5k are set up to.
These are the cards I used:
http://www.mini-box.com/s.nl/it.A/id.387/.f

I have run a saturated iPerf flow on a conducted testbed with both
stations being inside RF-shielding boxes. They are set to 802.11a
mode, on channel 1. I then parse the trace, looking for ACK-DATA
pairs, and calculating the time difference between them. From this, I
remove the TX_TIME of the DATA frame, as well as a DIFS:

ACK_TIMESTAMP + DIFS + CONTENTION_TIME + DATA_TX_TIME = DATA_TIMESTAMP

which will leave me with the CONTENTION_TIME. Dividing this time by a
SLOT_TIME will give me the slot which was chosen by the hardware.


According to the driver, in ath5k.h:

#define AR5K_TUNE_CWMIN                15

CWMIN is initialised to 15.

The actual distribution of contention slots I'm observing resembles this:

Slot Number,Count
0,1315
1,1302
2,1249
3,1291
4,1347
5,1219
6,1249
7,0
8,0
9,0
<truncated>

as well as 1360 frames which came in with a negative CONTENTION_TIME.

Ignoring the fact that some frames are coming up with a negative
CONTENTION_TIME (which potentially points to another problem), what is
being observed here is that CW_MIN appears to start at 7, rather than
the 15 which it should be.

I'm just wondering if anyone would have any idea why this is occurring?

Thanks,

--
Jonathan Guerin

PS sorry for the double-post, the system complained as my message was
originally in HTML

       reply	other threads:[~2010-09-14  5:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTi=azJS6bn7-=Bbb--ibACaQWqv4ZGLMUpfxynm7@mail.gmail.com>
2010-09-14  5:53 ` Jonathan Guerin [this message]
2010-09-15  3:40   ` [support] ath5k contention windows Jonathan Guerin
2010-09-15  3:48     ` [ath5k-devel] " Bruno Randolf
2010-09-14 17:39 ` Bob Copeland
2010-09-14 23:07   ` Jonathan Guerin
2010-09-15  0:44     ` Jonathan Guerin
2010-09-15  1:47       ` Bruno Randolf
2010-09-15  1:58         ` Jonathan Guerin
2010-09-14 22:48 ` Nick Kossifidis
2010-09-14 23:07   ` Jonathan Guerin
2010-09-15  0:58     ` Bruno Randolf
2010-09-15  1:06       ` Jonathan Guerin
2010-09-15  3:04         ` Bob Copeland
2010-09-15  3:20           ` Jonathan Guerin

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='AANLkTikvdkR=w-vGL=0LHnxQSibfoFBpuhLwjJZWVCuM@mail.gmail.com' \
    --to=jonathan@guerin.id.au \
    --cc=ath5k-devel@lists.ath5k.org \
    --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.