From: Sujith <m.sujith@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
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: Mon, 27 Oct 2008 19:55:02 +0530 [thread overview]
Message-ID: <18693.53054.116942.355275@localhost.localdomain> (raw)
In-Reply-To: <1224773201.6002.35.camel@johannes.berg>
Johannes Berg wrote:
> 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?
I wasn't aware of this parameter at all. Looks useful.
Atheros HW reports the Block Ack bitmap of the entire aggregate.
So passing that up to mac80211, and letting mac80211 handle retransmissions would work.
I am not sure about Intel.
Sujith
next prev parent reply other threads:[~2008-10-27 14:27 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 [this message]
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=18693.53054.116942.355275@localhost.localdomain \
--to=m.sujith@gmail.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