Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Tomas Winkler" <tomasw@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: Sujith <m.sujith@gmail.com>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Luis Rodriguez" <Luis.Rodriguez@atheros.com>
Subject: Re: [RFC] mac80211: Re-enable aggregation
Date: Tue, 28 Oct 2008 16:24:06 +0200	[thread overview]
Message-ID: <1ba2fa240810280724i54bfc61cqd2fde19bc37e3639@mail.gmail.com> (raw)
In-Reply-To: <1225123449.3796.24.camel@johannes.berg>

On Mon, Oct 27, 2008 at 6:04 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Mon, 2008-10-27 at 17:56 +0200, Tomas Winkler wrote:
>
>> In addition iwlwifi HW release TX packets in order to mac80211 i.e. no
>> need to maintain the transition window
>> so simple flag maybe shell revert the flow into regular tx response
>> flow in mac80211.
>> Only rate scaling is aware that the packets were transmitted
>> aggregated, we did some hacking there around this it should be cleaned
>> up.
>
> I wonder how we're going to pass them down to the driver anyway. And how
> about rate control, is that really done per sub-frame? Does that make
> any sense?

Sub frame? This is bit misleading in this context .This is not AMSDU.
This is rather a regular frame to be sent in a burst.

>I'm thinking that if we pass a fraglist down for the ampdu,

If you are able to do this you can also build AMSDU frame from the
frames, in AMPDU i prefer the streaming approach
and the decision about how many frames get into current TXOP is pushed
as low as possible, But maybe again I'm seeing this from iwlwifi
perspective.

> then we should have the fraglist in tx status too, in one go... If rate
> control is per subframe maybe it just needs to be made aware to walk the
> fraglist?

The rate scale should be aware of aggregation in order to be more
responsive (consider each aggregation as single transition) while
frame completion should be in order to preserve ordered definition of
802.11. protocol to upper layers (only completed sub window is
released up)

Tomas

  reply	other threads:[~2008-10-28 14:24 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20  8:22 [RFC] mac80211: Re-enable aggregation Sujith
2008-10-20  8:31 ` Johannes Berg
2008-10-20  8:35   ` Luis R. Rodriguez
2008-10-20  8:45     ` Johannes Berg
2008-10-20  8:47       ` Sujith
2008-10-20  8:55         ` Luis R. Rodriguez
2008-10-20  8:57           ` Johannes Berg
2008-10-20  9:01             ` Luis R. Rodriguez
2008-10-20  9:04               ` Johannes Berg
2008-10-20  9:05                 ` Luis R. Rodriguez
2008-10-20  9:11                 ` Sujith
2008-10-20  8:57       ` Luis R. Rodriguez
2008-10-20  8:58   ` Sujith
2008-10-20  9:12     ` Johannes Berg
2008-10-20  9:31       ` Sujith
2008-10-20  9:38         ` Johannes Berg
2008-10-20 10:35           ` Sujith
2008-10-20 12:22             ` Johannes Berg
2008-10-20 18:03               ` Sujith
2008-10-20 21:46                 ` Tomas Winkler
2008-10-21  6:46                   ` Johannes Berg
2008-10-21  7:18                   ` Sujith
2008-10-22 10:03                   ` Johannes Berg
2008-10-22 11:59                     ` Tomas Winkler
2008-10-22 17:22                       ` Johannes Berg
2008-10-23  8:57                         ` Sujith
2008-10-23 14:46                           ` Johannes Berg
2008-10-27 14:25                             ` Sujith
2008-10-27 15:04                               ` Johannes Berg
2008-10-27 15:56                                 ` Tomas Winkler
2008-10-27 16:04                                   ` Johannes Berg
2008-10-28 14:24                                     ` Tomas Winkler [this message]
2008-10-22 10:00                 ` Johannes Berg
2008-10-22 11:41                   ` Tomas Winkler
2008-10-22 17:24                     ` Johannes Berg
2008-10-23  9:31                   ` Sujith
2008-10-23 14:45                     ` Johannes Berg
2008-10-23 17:23                       ` Luis R. Rodriguez
2008-10-23 18:31                         ` Tomas Winkler
2008-10-23 20:18                           ` Luis R. Rodriguez
2008-10-23 21:17                             ` Tomas Winkler
2008-10-31  1:26                               ` Luis R. Rodriguez
2008-10-27 14:11                       ` Sujith
2008-10-27 15:07                         ` Johannes Berg
2008-10-20  9:14     ` Luis R. Rodriguez
2008-10-20  9:24       ` Johannes Berg
2008-10-20 10:07         ` Sujith
2008-10-20 10:15           ` 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=1ba2fa240810280724i54bfc61cqd2fde19bc37e3639@mail.gmail.com \
    --to=tomasw@gmail.com \
    --cc=Luis.Rodriguez@atheros.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=m.sujith@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