From: Johannes Berg <johannes@sipsolutions.net>
To: Daniel Halperin <dhalperi@cs.washington.edu>
Cc: wwguy <wey-yi.w.guy@intel.com>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: bug: iwlwifi, aggregation, and mac80211's reorder buffer
Date: Tue, 15 Mar 2011 19:41:26 +0100 [thread overview]
Message-ID: <1300214486.4139.6.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <AANLkTinfEU2HNAg7aTmMgSrR6vVyVwLbFmpcP9TL4GyK@mail.gmail.com>
On Tue, 2011-03-15 at 11:16 -0700, Daniel Halperin wrote:
> There's still something off about the window size: unlike with ath9k,
> the receiver does continually print out warnings about advancing its
> window. There's something very fishy here: for any given aggregation
> session, the part of the sequence number space this happens is always
> the same! Really weird. Here's a log from 3 agg sessions in a row,
> just running simple TCP iperf:
>
> [341221.679710] New seq exceeds buffering window: 283, 250
Ok thanks for the patch, I'll still reply here though.
> [341398.950019] iwlagn 0000:03:00.0: iwlagn_tx_agg_start on ra =
> 00:16:ea:c3:b3:8e tid = 0
> [341401.790964] New seq exceeds buffering window: 2335, 2304
So the delta is always 31, it seems? Is iwlwifi consistently sending
batches of 32 instead of the advertised 31?
Also -- don't get confused, the tx_agg_start is on its own TX agg
session, but the new seq stuff is on its RX agg session.
johannes
next prev parent reply other threads:[~2011-03-15 18:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 8:11 bug: iwlwifi, aggregation, and mac80211's reorder buffer Daniel Halperin
2011-03-11 8:13 ` Guy, Wey-Yi
2011-03-13 19:59 ` Daniel Halperin
2011-03-14 0:47 ` wwguy
2011-03-14 18:16 ` Daniel Halperin
2011-03-15 11:51 ` Johannes Berg
2011-03-15 12:52 ` Johannes Berg
2011-03-15 18:16 ` Daniel Halperin
2011-03-15 18:29 ` Johannes Berg
2011-03-15 18:31 ` Daniel Halperin
2011-03-15 18:33 ` Daniel Halperin
2011-03-15 18:41 ` Johannes Berg [this message]
2011-03-15 18:47 ` Daniel Halperin
2011-03-15 18:52 ` Johannes Berg
2011-03-14 16:24 ` Johannes Berg
2011-03-14 17:38 ` Daniel Halperin
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=1300214486.4139.6.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dhalperi@cs.washington.edu \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=wey-yi.w.guy@intel.com \
/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).