From: Christian Lamparter <chunkeey@googlemail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "linux-wireless" <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH v2] mac80211: temporarily disable reorder release timer
Date: Fri, 8 Oct 2010 23:57:04 +0200 [thread overview]
Message-ID: <201010082357.04992.chunkeey@googlemail.com> (raw)
In-Reply-To: <AANLkTi=Pe7tt+As0_Kzjt0PB=cHO_eSO+Qs8dy2o+Mbd@mail.gmail.com>
On Friday 08 October 2010 23:22:57 Luis R. Rodriguez wrote:
> On Fri, Oct 8, 2010 at 1:49 PM, Christian Lamparter
> <chunkeey@googlemail.com> wrote:
> > On Friday 08 October 2010 22:40:39 Luis R. Rodriguez wrote:
> >> On Fri, Oct 8, 2010 at 1:35 PM, Christian Lamparter
> >> <chunkeey@googlemail.com> wrote:
> >> > Several serve threading problems in the current
> >> > release reorder timer implementation have been
> >> > discovered.
> >> >
> >> > A lengthy discussion - which lists some of the
> >> > pitfalls and possible solutions - can be found at:
> >> > http://marc.info/?t=128635927000001
> >> >
> >> > But due to the complicated nature of the subject and
> >> > the imminent advent of a new -rc cycle, it was
> >> > decided to disable the feature for the time being.
> >> >
> >> > Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
> >>
> >> This patch lacks documentation of the impact of this patch, while it
> >> may fix a lock issue, the does not address what happens when the patch
> >> is actually applied.
> > ? It just disables the timer. The actual reorder code
> > is left untouched, everything is the same as in Linus'
> > 2.6.36-rcX tree.
> >
> > Or what impact are you talking about?
>
> The timer is what I'm talking about, we don't run then
> ieee80211_release_reorder_timeout() right so we don't clear stale
> frames on aggregates.
What? Who told you that? Because that's just misinformation.
This patch doesn't touch/disable the reorder release mechanism
(ieee80211_sta_reorder_release) at all.
It only disarms the timer which would clean out frames after
approx. 100ms.
And even without the timer, there are still three other ways
for cleaning out "stale" frame aggregates.
1. BAR from peer (ieee80211_rx_h_ctrl)
2. BAW window overflow (ieee80211_sta_manage_reorder_buf,
part of the aMPDU rx path - executed for every received
MPDU)
3. ieee80211_sta_reorder_release (automatically called by
ieee80211_sta_manage_reorder_buf when a reorder gaps
are opening up.)
(I repeat, the rx path logic & behavior is identical to
vanilla 2.6.36-rcX)
> What impact does this have?
everything is back to stock, at least for now?
see:
http://marc.info/?l=linux-wireless&m=128656352920957
"I don't like reverting these patches, but maybe we should
simply comment out the code that arms the timer, thereby
disabling all of it, while we work on this?"
-- Johannes
Best regards,
Christian
prev parent reply other threads:[~2010-10-08 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 20:35 [PATCH v2] mac80211: temporarily disable reorder release timer Christian Lamparter
2010-10-08 20:40 ` Luis R. Rodriguez
2010-10-08 20:49 ` Christian Lamparter
2010-10-08 21:22 ` Luis R. Rodriguez
2010-10-08 21:57 ` Christian Lamparter [this message]
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=201010082357.04992.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.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).