linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Benoit PAPILLAULT <benoit.papillault@free.fr>
Cc: Maxim Levitsky <maximlevitsky@gmail.com>,
	Derek Smithies <derek@indranet.co.nz>,
	ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net, wally@theblackmoor.net,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [ath5k-devel] Unusually low speeds with ath5k and iwl3945
Date: Tue, 25 Nov 2008 23:47:38 +0100	[thread overview]
Message-ID: <492C808A.20403@openwrt.org> (raw)
In-Reply-To: <492C55FC.2040506@free.fr>

Benoit PAPILLAULT wrote:
> Felix Fietkau a =E9crit :
>> While reading the code for calculating the frame duration, i noticed
>> something odd: It doesn't seem to be taking into account the short
>> vs long preamble distinction for ERP rates. IMHO this might be causi=
ng
>> issues like this. I've seen similar behaviour a long time ago when t=
esting
>> iwl3945 against a Broadcom AP with exactly the same throughput drop =
(500-
>> 600 kbits/s).
>> When I analyzed the problem with an extra monitor mode card, I found=
 out
>> that the throughput drop is caused by a huge number of retransmissio=
ns,
>=20
> In the test I've done, there was no retransmission at all (no
> duplicates). I don't save a capture file, so I cannot tell for sure.
Which test specifically? iwl3945 or ath5k?
If ath5k doesn't show any retransmissions, the problem might not be
related. Please do make some logs of the throughput issue and then
some more of the same kind of traffic without throughput issues
(same card, same driver).

> What is the code computing frame duration you are referring to? How i=
t
> could affect the hardware behavior?
I looked at it again and now I don't think it's the cause anymore. I
 did some comparisons against other stacks/drivers and this part
seems correct after all.

- Felix
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-11-25 22:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21 20:28 Unusually low speeds with ath5k and iwl3945 Maxim Levitsky
2008-11-22  0:52 ` Bob Copeland
2008-11-22  3:46   ` [ath5k-devel] " Derek Smithies
2008-11-22 12:33     ` Maxim Levitsky
2008-11-24  7:34       ` Benoit PAPILLAULT
2008-11-24  9:43         ` Felix Fietkau
2008-11-24 10:34           ` Johannes Berg
2008-11-25 19:46           ` Benoit PAPILLAULT
2008-11-25 22:47             ` Felix Fietkau [this message]
2008-11-22 10:16 ` [ipw3945-devel] " Rafał Miłecki
2008-12-03 16:55 ` reinette chatre
2008-12-03 17:09   ` Maxim Levitsky
2008-12-03 17:36     ` reinette chatre

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=492C808A.20403@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=benoit.papillault@free.fr \
    --cc=derek@indranet.co.nz \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maximlevitsky@gmail.com \
    --cc=wally@theblackmoor.net \
    /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).