From: Johannes Berg <johannes@sipsolutions.net>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [WIP] mac80211: AMPDU rx reorder timeout timer
Date: Tue, 27 Jul 2010 10:37:25 +0200 [thread overview]
Message-ID: <1280219845.19098.4.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <201007270820.25347.chunkeey@googlemail.com>
On Tue, 2010-07-27 at 08:20 +0200, Christian Lamparter wrote:
> This (rather _unfinished_ :-D ) patch adds a timer which
> if trigger schedules the automatic release of all expired
> A-MPDU frames. This implementation has the advantage that
> all queued-up MPDU will now arrive in the network core
> within a timely manner.
>
> In my "experiments", the patch helped to ironed out the
> sudden throughput drops that have been _killing_ my
> average tcp performance ever since I can remember.
But why is your BA session so damaged to start with? This is not a
normal situtation!
> But there is a catch: The logs will quickly fill up with:
> "release an RX reorder frame due to timeout on earlier frames".
> and the package loss will goes through the roof...
>
> Now, I can think of several reasons why this could happen:
> 1. we don't wait long enough for the HT peer to
> finish their _retry_ procedure?
>
> 2. previously - when the stream simply _stopped_ - we had
> to wait until the tcp retry kick in again. So we had
> some "silent" periods and therefore less noise from
> the reordering code?
>
> 3. ->bugs<- but where are they?
I'm having a hard time understanding this patch, can you split out the
no-op code reorg parts or explain what it does?
johannes
next prev parent reply other threads:[~2010-07-27 8:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 6:20 [WIP] mac80211: AMPDU rx reorder timeout timer Christian Lamparter
2010-07-27 8:37 ` Johannes Berg [this message]
2010-07-28 15:16 ` Christian Lamparter
2010-07-28 15:17 ` [WIP 1/3] mac80211: put rx handlers into seperate functions Christian Lamparter
2010-07-28 15:21 ` [WIP 2/3] mac80211: remove (now) unused rate function parameters Christian Lamparter
2010-07-28 15:21 ` [WIP 3/3] mac80211: AMPDU rx reorder timeout timer Christian Lamparter
2010-08-02 13:16 ` [PATCH " Christian Lamparter
2010-08-02 13:24 ` Johannes Berg
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=1280219845.19098.4.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=chunkeey@googlemail.com \
--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).