From: Felix Fietkau <nbd@openwrt.org>
To: Krishna Chaitanya <chaitanya.mgit@gmail.com>,
Emmanuel Grumbach <egrumbach@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [RFC v4] mac80211: add A-MSDU tx support
Date: Mon, 8 Feb 2016 12:04:05 +0100 [thread overview]
Message-ID: <56B87625.6040206@openwrt.org> (raw)
In-Reply-To: <CABPxzY+dgMWDeQ=_c0xyFq0g7HcP459b5Ypy3OoUwjDi+eooMA@mail.gmail.com>
On 2016-02-08 10:54, Krishna Chaitanya wrote:
> On Mon, Feb 8, 2016 at 2:56 PM, Emmanuel Grumbach <egrumbach@gmail.com> wrote:
>> On Mon, Feb 8, 2016 at 10:38 AM, Felix Fietkau <nbd@openwrt.org> wrote:
>>> Requires software tx queueing support. frag_list support (for zero-copy)
>>> is optional.
>>>
>>> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
>>> ---
>>
>>
>> Ok - looks fine, but... and here comes the hard stuff.
>> The frame size in the PLCP is limited in a way that you can't - from a
>> spec POV - enable A-MSDU for low rates. Of course, you don't want to
>> do that for low rates at all regardless of the spec.
>> Since you build the A-MSDU in the mac80211 Tx queue which is not aware
>> of the link quality, how do we prevent A-MSDU if the rate is low /
>> dropping.
>> I'd even argue that when the rates get lower, you'll have more
>> packets piling up in the software queue and ... even more chance to
>> get A-MSDU in the exact case where you really want to avoid it?
>
> Similar to triggering AMPDU setup, we should put this control
> in RC (minstrel) to start/stop AMSDU based on link quality/if the rates
> drop below a pre-defined MCS (or) only for best-throughput rates.
I think starting/stopping A-MSDU based on the rate is a bad idea.
Even with low rates, using A-MSDU can be a good thing (especially for
TCP ACKs), it just needs different size limits.
- Felix
next prev parent reply other threads:[~2016-02-08 11:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 8:38 [RFC v4] mac80211: add A-MSDU tx support Felix Fietkau
2016-02-08 9:26 ` Emmanuel Grumbach
2016-02-08 9:54 ` Krishna Chaitanya
2016-02-08 10:26 ` Emmanuel Grumbach
2016-02-08 11:09 ` Krishna Chaitanya
2016-02-08 11:17 ` Michal Kazior
2016-02-08 11:15 ` Felix Fietkau
2016-02-08 12:31 ` Emmanuel Grumbach
2016-02-08 11:04 ` Felix Fietkau [this message]
2016-02-08 11:06 ` Krishna Chaitanya
2016-02-08 11:23 ` Felix Fietkau
2016-02-08 12:36 ` Emmanuel Grumbach
2016-02-08 17:46 ` Dave Taht
2016-02-08 18:13 ` Juliusz Chroboczek
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=56B87625.6040206@openwrt.org \
--to=nbd@openwrt.org \
--cc=chaitanya.mgit@gmail.com \
--cc=egrumbach@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