From: Johannes Berg <johannes@sipsolutions.net>
To: Karl Beldan <karl.beldan@gmail.com>
Cc: Blaise Gassend <blaise@suitabletech.com>,
linux-wireless@vger.kernel.org,
Catalin Drula <catalin@suitabletech.com>,
Alap Modi <amodi@arubanetworks.com>
Subject: Re: QoS Data packets causing massive packet loss in ieee80211_sta_manage_reorder_buf.
Date: Wed, 20 Nov 2013 12:06:09 +0100 [thread overview]
Message-ID: <1384945569.14295.5.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20131120110157.GA6993@magnum.frso.rivierawaves.com> (sfid-20131120_120236_416727_B8F79832)
On Wed, 2013-11-20 at 12:01 +0100, Karl Beldan wrote:
> On Wed, Nov 20, 2013 at 02:15:27AM -0800, Blaise Gassend wrote:
> > Hi Johannes,
> >
> > Thanks for the quick reply!
> >
> > > I think we just need to skip reorder processing for multicast, since
> > > they won't be aggregated anyway?
> > >
> > > http://p.sipsolutions.net/d00799dd2201676a.txt
> >
> > This patch works like a charm for my current predicament. But is it
> > actually written somewhere that multicast packets can't be aggregated?
> > I can't find any place that says they can't, but I'm not authoritative
> > by any means.
> >
> There's a chapter "A-MPDU aggregation of group addressed data frames" in
> the specs, however I haven't seen this yet.
Even then though, I don't think there would be any block-ack session,
and thus you wouldn't be able to use the reorder buffer anyway, right?
johannes
next prev parent reply other threads:[~2013-11-20 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 8:41 QoS Data packets causing massive packet loss in ieee80211_sta_manage_reorder_buf Blaise Gassend
2013-11-20 8:48 ` Johannes Berg
2013-11-20 10:15 ` Blaise Gassend
2013-11-20 11:01 ` Karl Beldan
2013-11-20 11:06 ` Johannes Berg [this message]
2013-11-20 11:16 ` Karl Beldan
2013-11-20 11:25 ` Karl Beldan
2013-11-20 11:39 ` 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=1384945569.14295.5.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=amodi@arubanetworks.com \
--cc=blaise@suitabletech.com \
--cc=catalin@suitabletech.com \
--cc=karl.beldan@gmail.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).