From: "Tomas Winkler" <tomasw@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: Friedrich.Beckmann@infineon.com, linux-wireless@vger.kernel.org, j@w1.fi
Subject: Re: iwlwifi aggregation info
Date: Thu, 7 Aug 2008 01:05:53 +0300 [thread overview]
Message-ID: <1ba2fa240808061505u37d4f300n48d0d45918b34a35@mail.gmail.com> (raw)
In-Reply-To: <1218059104.23048.81.camel@johannes.berg>
On Thu, Aug 7, 2008 at 12:45 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
>
>> When that is not the case, however, we disagree. I think that because
>> aggregation isn't a QoS mechanism, it should behave the same way as in
>> the case where no stations have aggregation enabled, and stall the whole
>> queue. On the other hand, you think it is a QoS mechanism, and let
>> streams for the fast stations be interleaved with the slow station,
>> leaving only frames for the slow station piling up.
>
> I just found IEEE 802.11-2007 subclause 9.10 which actually explains all
> the block-ack business without aggregation, but I assume that
> aggregation now just means that instead of sending
> mpdu + sifs + (mpdu + sifs)* + blockackreq
> you send simply
> a-mpdu
>
> I see nothing in 9.10 that supports the view that aggregation/block-ack
> should create a new traffic stream.
It doesn't have to be spelled, it's clear from the fact that traffic
is defined by <TID,RA> pair.
A-MPDU stuff is simplified version of what you've read there.
Tomas
next prev parent reply other threads:[~2008-08-06 22:05 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 11:32 iwlwifi aggregation info Johannes Berg
2008-07-29 11:36 ` Johannes Berg
2008-07-29 12:25 ` Tomas Winkler
2008-07-29 12:27 ` Johannes Berg
2008-07-29 12:35 ` Tomas Winkler
2008-07-29 12:53 ` Johannes Berg
2008-07-29 13:04 ` Tomas Winkler
2008-07-29 13:07 ` Johannes Berg
2008-07-29 13:18 ` Tomas Winkler
2008-07-29 13:23 ` Johannes Berg
2008-07-29 13:43 ` Tomas Winkler
2008-07-29 13:46 ` Johannes Berg
2008-07-29 14:06 ` Tomas Winkler
2008-07-29 14:21 ` Johannes Berg
2008-07-29 15:55 ` Tomas Winkler
2008-07-30 9:53 ` Johannes Berg
2008-07-30 11:03 ` Friedrich.Beckmann
2008-07-30 13:19 ` Johannes Berg
2008-07-30 13:45 ` Tomas Winkler
2008-07-30 13:50 ` Johannes Berg
2008-07-30 13:59 ` Tomas Winkler
2008-07-30 15:19 ` Johannes Berg
2008-07-30 16:08 ` Tomas Winkler
2008-07-31 13:05 ` Johannes Berg
2008-07-31 18:14 ` Tomas Winkler
2008-07-31 18:23 ` Johannes Berg
2008-07-31 19:16 ` Tomas Winkler
2008-08-01 12:09 ` Johannes Berg
2008-08-01 12:40 ` Tomas Winkler
2008-08-01 12:54 ` Johannes Berg
2008-08-06 21:45 ` Johannes Berg
2008-08-06 22:05 ` Tomas Winkler [this message]
2008-08-06 22:31 ` Tomas Winkler
2008-08-07 11:13 ` mac80211 aggregation (was: iwlwifi aggregation info) Johannes Berg
2008-08-07 12:21 ` Friedrich.Beckmann
2008-08-07 12:31 ` Johannes Berg
2008-08-07 13:00 ` Friedrich.Beckmann
2008-07-30 12:01 ` iwlwifi aggregation info Tomas Winkler
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=1ba2fa240808061505u37d4f300n48d0d45918b34a35@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=Friedrich.Beckmann@infineon.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--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