Linux wireless drivers development
 help / color / mirror / Atom feed
From: Sujith <Sujith.Manoharan@atheros.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Sujith Manoharan <Sujith.Manoharan@Atheros.com>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
	"tomasw@gmail.com" <tomasw@gmail.com>
Subject: Re: [RFC] mac80211: Re-enable aggregation
Date: Mon, 20 Oct 2008 15:01:23 +0530	[thread overview]
Message-ID: <18684.20459.335157.171344@gargle.gargle.HOWL> (raw)
In-Reply-To: <1224493957.18024.47.camel@johannes.berg>

Johannes Berg wrote:
> Can you change your quote string from " > " to "> "? Just asking, if you
> can't/don't want to that's fine, it just always confuses me for a
> second. I really should try to figure out if I can convince my mailer to
> highlight " > " indented text as quote too.

Sure, adding (setq vm-included-text-prefix "> ") in my .emacs did the trick. :)

> > Well, currently ath9k maintains a buffer list for each tid.
> > When mac80211 sends down a frame, if the recipient has an aggr. session going,
> > it is appended to the tid's buffer list. Non-HT frames are sent out immediately.
> 
> Incidentally, why the distinction between HT and non-HT frames?

HT frames for aggregation enabled STAs are processed in the TX completion path, so
they are buffered.

> > On TX completion, we run through all the ACs, STAs and TIDs and send out pending
> > frames as aggregates.
> 
> So basically you can always have one frame or one aggregation
> "pack" (for lack of a better word) queued to the hw?
> 

I am not sure, I should check.

> > mac80211 can probably help by maintaining the TX state for each TID, maintain the
> > buffer list, etc.  and provide appropriate mechanisms for drivers to obtain pending
> > frames as and when needed.
> 
> Sure could. Intel's hw would probably like a way to say "stop this TID"
> and "wake this TID" which is what they tried to do using real queues.
> mac80211 could queue up the frames in per-station state and provide a
> functions like
> 
> ieee80211_stop_aggr_stream(struct ieee80211_sta *sta, u8 tid);
> ieee80211_wake_aggr_stream(struct ieee80211_sta *sta, u8 tid);
> 
> or something like that. Then those frames would flow into the right
> queue. We might need a multi-layer start/stop management but we already
> do, we've just managed to get away without it without tx stalls. Or they
> just haven't been reported yet.
> 

Makes sense, ath9k currently has a similar set of functions ( pausing/resuming TIDs).
How would the pending frames for each TID be managed ?
Will the driver be able to pull them as and when needed or would mac80211
push them down on checking if the TID is awake ?

Sujith

  reply	other threads:[~2008-10-20  9:33 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 [this message]
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
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=18684.20459.335157.171344@gargle.gargle.HOWL \
    --to=sujith.manoharan@atheros.com \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=tomasw@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