From: matthieu castet <castet.matthieu@free.fr>
To: Michael Buesch <mb@bu3sch.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: b43 : under high load, ack are lost
Date: Sun, 24 May 2009 23:42:02 +0200 [thread overview]
Message-ID: <4A19BF2A.3030101@free.fr> (raw)
In-Reply-To: <200905211747.43882.mb@bu3sch.de>
Michael Buesch wrote:
> On Wednesday 20 May 2009 23:09:47 matthieu castet wrote:
>> I see also some period were the AP seem to drop all packet.
>> I am wondering if it can be due to slow recalibration.
>> Do you now how much take calibration were mac is down ?
>
> I think you should try without QoS.
> Try specifying the qos=0 module parameter to b43.
> If that does not work, additionally apply the following patch.
> I think there are some problems with QoS and I think somebody reported some bugs
> some time ago. I think they are still not addressed.
Thank you for your help.
First I used a ipw2200 for monitoring traffic, but it seems it doesn't
not capture all packets. That what explain the strange pattern I saw
before (missing ack or 2 following ack).
The qos disable doesn't seem to help much. There still some period where
the AP seem blind.
Disabling pwork doesn't help, but some stuff is still done with
b43_phy_txpower_check on tx path.
I will try to investigate more. A quick workaround is to increase the
number of retry on my station.
yes.
Matthieu
next prev parent reply other threads:[~2009-05-24 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-17 9:08 b43 : under high load, ack are lost Matthieu CASTET
2009-05-20 20:37 ` matthieu castet
2009-05-20 21:09 ` matthieu castet
2009-05-20 21:34 ` Michael Buesch
2009-05-21 10:16 ` Michael Buesch
2009-05-21 15:47 ` Michael Buesch
2009-05-24 21:42 ` matthieu castet [this message]
2009-05-24 21:53 ` Michael Buesch
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=4A19BF2A.3030101@free.fr \
--to=castet.matthieu@free.fr \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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).