Linux wireless drivers development
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Krishna Chaitanya <chaitanya.mgit@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Tx AMSDU Support
Date: Tue, 15 Jan 2013 13:06:36 +0100	[thread overview]
Message-ID: <50F5464C.4020608@openwrt.org> (raw)
In-Reply-To: <CABPxzYL1LM-XAAb1RomgcM=O9Ma=KJZcbmEgTA678FSFuT8QMg@mail.gmail.com>

On 2013-01-15 11:20 AM, Krishna Chaitanya wrote:
> Hi Johannes,
> 
> Is there any work in progress/planned related to Tx AMSDU logic in mac80211?
> Even though only Rx is mandatory, but to test the Rx we need the Tx.
> 
> I see that the support is there in mwifiex(marvell's) driver. So is
> there any patent/legal issue before we can implement one?
The issue with AMSDU Tx is a technical one, not a legal one: A-MSDU
aggregation needs a queue and some buffering to properly work, A-MPDU
needs the same. A-MPDU is typically implemented in the driver/firmware.

Doing extra buffering/queueing in mac80211 is not a good idea, as it
would add significant extra latency in the Tx path, so A-MSDU
aggregation really needs to be done on the same queue.

For implementing A-MSDU in ath9k, my plan is to share the per-sta-tid
A-MPDU driver queues between mac80211 and ath9k. That way I can keep the
logic inside mac80211 with no added buffering/latency. I might even be
able to have an A-MSDU aggregation fastpath that happens before 802.11
header encapsulation.

The problem with this approach is that it doesn't work with drivers
using hardware/firmware based A-MPDU aggregation. Such drivers will
probably either have to do A-MSDU in firmware as well, or

- Felix

  parent reply	other threads:[~2013-01-15 12:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15 10:20 Tx AMSDU Support Krishna Chaitanya
2013-01-15 11:23 ` Johannes Berg
2013-01-16  4:09   ` Krishna Chaitanya
2013-01-16 23:05     ` Adrian Chadd
2013-01-16 23:23       ` Johannes Berg
2013-01-17  8:44         ` Krishna Chaitanya
2013-01-17 19:29           ` Bing Zhao
2013-01-18  6:15             ` Krishna Chaitanya
2013-01-15 12:06 ` Felix Fietkau [this message]
2013-01-16  4:07   ` Krishna Chaitanya

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=50F5464C.4020608@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=chaitanya.mgit@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /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