From: Johannes Berg <johannes@sipsolutions.net>
To: Sujith <Sujith.Manoharan@atheros.com>
Cc: Tomas Winkler <tomasw@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: Thu, 23 Oct 2008 16:46:41 +0200 [thread overview]
Message-ID: <1224773201.6002.35.camel@johannes.berg> (raw)
In-Reply-To: <18688.15460.336059.400706@gargle.gargle.HOWL>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
On Thu, 2008-10-23 at 14:27 +0530, Sujith wrote:
> > Yeah, this is something we definitely need to work out. We haven't even
> > managed to decide yet how aggregated packets are given to the driver :)
> > I think for atheros and bcom a model where mac80211 decides pretty much
> > everything and hands the driver a list of skbs to aggregate would work
> > best, but then I think that wouldn't work with your hw at all.
> >
>
> Retransmission of unacked frames is done within the driver, in ath9k.
> In case of retry exhaustion (failed transmission), we do what Intel does,
> i.e, request for a BAR to be sent out.
We have this "ampdu_ack_map" parameter in the TX status which could be
set by the driver. But that assumes we only want a single TX status for
all A-MPDU frames, do we really? Or do we want to split them up and
handle it all in mac80211?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-10-23 14:47 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 [this message]
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=1224773201.6002.35.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=Luis.Rodriguez@Atheros.com \
--cc=Sujith.Manoharan@atheros.com \
--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