linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: matthieu castet <castet.matthieu@free.fr>
To: linux-wireless@vger.kernel.org
Subject: Re: b43 : under high load, ack are lost
Date: Wed, 20 May 2009 20:37:11 +0000 (UTC)	[thread overview]
Message-ID: <loom.20090520T203218-265@post.gmane.org> (raw)
In-Reply-To: loom.20090517T085823-487@post.gmane.org

Matthieu CASTET <castet.matthieu@...> writes:

> 
> Hi,
> 
> I use a 4306 (core rev 5) with compat-wireless-2009-05-08 as wireless driver
> and
> 4.150.10.5 firmware.
> My station is an airo card in wpa-psk mode (802.11b).
> 
> After resolving my beacon problem [1], when I download at max speed my 
> station
> disconnect from AP because "LostSync-MaxRetry".
> After looking in my station statistic it seems the retry (RetryLong) are due 
> to
> noack received from the AP.
I take a monitor trace of the trafic and I see weird stuff from the b43 AP, 
there is lot of case of :
- client send data to AP
- AP send data to client
- ack from client
- AP send data to client
- ack from client
- AP send data to client
- ack from client
- ack from AP (for 1 packet)


Sometimes it is :
- client send data to AP
- AP send data to client
- ack from client
- AP send data to client
- ack from client
- AP send data to client
- ack from client
- client resend data to AP
- ack from AP
- client send data to AP
- ack from AP
- ack from AP (for 1 packet)


It seems like ack are queued somewhere with low priority.


  reply	other threads:[~2009-05-20 20:37 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 [this message]
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
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=loom.20090520T203218-265@post.gmane.org \
    --to=castet.matthieu@free.fr \
    --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 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).