From: Johannes Berg <johannes@sipsolutions.net>
To: Karl Beldan <karl.beldan@gmail.com>
Cc: Helmut Schaa <helmut.schaa@googlemail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Karl Beldan <karl.beldan@rivierawaves.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Subject: Re: [PATCH] mac80211: send {add,del}ba on AC_VO like other mgmt frames, as per spec
Date: Wed, 22 Jan 2014 20:21:35 +0100 [thread overview]
Message-ID: <1390418495.4334.49.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20140122191610.GD18365@magnum.frso.rivierawaves.com> (sfid-20140122_201711_730750_BBD5790C)
On Wed, 2014-01-22 at 20:16 +0100, Karl Beldan wrote:
> > Given the fact that we only send the frame from
> > ieee80211_stop_tx_ba_cb() I don't see any problem. Even if we were to
> > send the frame directly after calling the ampdu_action, it seems it
> > would be fine, since the callback (now) requires sending the remaining
> > frames unaggregated. (Given that, I'm not even sure why we required the
> > packets to be sent unaggregated, Emmanuel, do you remember?)
> >
> I'd expect most device to not block ack such frames, and they'd be
> right to do so, sending them unaggregated seems the right thing to do.
Oh, I roughly remember now - we didn't want to separate the cases of us
sending a delBA and us receiving a delBA. If we receive a delBA, we
should stop sending aggregated frames immediately (actually for iwlwifi
the firmware will do that) or as quickly as possible, hence the
requirement
If we decide to tear down the session ourselves then we could continue
sending until later, but it's not worth it.
> So, I guess you are taking what I sent ?
Haven't really made up my mind yet ... I think it's more correct, so I
should, but I also don't really want to break the ralink drivers over
what seems to me to be a fairly small issue.
johannes
next prev parent reply other threads:[~2014-01-22 19:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 11:52 [PATCH] mac80211: send {add,del}ba on AC_VO like other mgmt frames, as per spec Karl Beldan
2014-01-22 12:34 ` Johannes Berg
2014-01-22 13:09 ` Karl Beldan
2014-01-22 13:33 ` Helmut Schaa
2014-01-22 15:28 ` Karl Beldan
2014-01-22 15:36 ` Helmut Schaa
2014-01-22 16:41 ` Karl Beldan
2014-01-22 18:51 ` Johannes Berg
2014-01-22 19:16 ` Karl Beldan
2014-01-22 19:21 ` Johannes Berg [this message]
2014-01-22 20:47 ` Helmut Schaa
2014-01-23 6:08 ` Grumbach, Emmanuel
2014-01-23 13:42 ` Helmut Schaa
2014-01-23 14:08 ` Johannes Berg
2014-01-23 19:06 ` [PATCH v2] mac80211: send {ADD,DEL}BA " Karl Beldan
2014-01-23 19:15 ` Johannes Berg
2014-01-23 19:38 ` Karl Beldan
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=1390418495.4334.49.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=emmanuel.grumbach@intel.com \
--cc=helmut.schaa@googlemail.com \
--cc=karl.beldan@gmail.com \
--cc=karl.beldan@rivierawaves.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).