From: "Tomas Winkler" <tomasw@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "Jouni Malinen" <j@w1.fi>,
"Ron Rindjunsky" <rindjon@googlemail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: HT action frame code
Date: Tue, 9 Sep 2008 12:52:02 +0300 [thread overview]
Message-ID: <1ba2fa240809090252u44c5a016m98845379ac213df9@mail.gmail.com> (raw)
In-Reply-To: <1220953379.31304.124.camel@johannes.berg>
On Tue, Sep 9, 2008 at 12:42 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Tue, 2008-09-09 at 12:41 +0300, Tomas Winkler wrote:
>
>> >> Meaning that other management frames are forward to user space while
>> >> BA action frames
>> >> are treated inside mac80211.
>> >
>> > Can you point out where? I don't see it.
>> It's should be visible in AP code Yi has posted, unfortunately don't
>> have it open right now. Anyhow since then the rx flow has changed a
>> lot as you know :) so it has to be reinvented.
>
> Ok, so it's not in the current code and I'm not entirely stupid for not
> finding it, heh :) I don't think I even still have the patches on this
> box so I won't look.
>
>> >> > Also, I'm not talking about the AP triggering the aggregation session,
>> >> > this is entirely done with the rate scaling right now, but about an
>> >> > associated STA wanting to start an aggregation session. Aren't
>> >> > aggregation sessions always triggered by whoever wants to send? So if a
>> >> > STA notices it has lots of upload going on it could want to trigger a BA
>> >> > session, which is something we don't currently support afaict.
>> >>
>> >> In iwl-agn-rs.c There is not difference if the peer is STA or AP. So
>> >> we support this already.
>> >
>> > Not sure what this has to do with the Intel RS algorithm?
>>
>> Just the trigger for aggregation is implemented there. Otherwise
>> nothing special.
>
> Well yes, but that just triggers when aggregation on our end, what I'd
> been thinking about was when the remote side wants to start aggregation.
There is some misunderstanding. I hope I'm explaining the problematic
part. Aggregation is always initialized by TX side it's one direction
only. So if there AP and STA wants to start aggregation. Both will
open a stream. The streams are independent.
Tomas
> johannes
>
next prev parent reply other threads:[~2008-09-09 9:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 14:22 HT action frame code Johannes Berg
2008-09-08 20:09 ` Jouni Malinen
2008-09-08 20:48 ` Tomas Winkler
2008-09-09 6:30 ` Johannes Berg
2008-09-09 6:33 ` Johannes Berg
2008-09-09 8:14 ` Tomas Winkler
2008-09-09 8:20 ` Johannes Berg
2008-09-09 8:46 ` Tomas Winkler
2008-09-09 8:52 ` Johannes Berg
2008-09-09 9:41 ` Tomas Winkler
2008-09-09 9:42 ` Johannes Berg
2008-09-09 9:52 ` Tomas Winkler [this message]
2008-09-09 9:55 ` Johannes Berg
2008-09-09 10:21 ` Tomas Winkler
2008-09-09 10:25 ` Johannes Berg
2008-09-09 10:27 ` Johannes Berg
2008-09-09 10:53 ` Tomas Winkler
2008-09-09 11:01 ` Johannes Berg
2008-09-09 11:29 ` [RFC] mac80211: make BA session handling independent of STA mode Johannes Berg
2008-09-09 12:28 ` 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=1ba2fa240809090252u44c5a016m98845379ac213df9@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=rindjon@googlemail.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