> On Jun 26, 2018, at 12:43 PM, Toke Høiland-Jørgensen wrote:
>
> There's a limit to the maximum aggregation size on VO and VI (for VO it
> is '1 packet' as Sebastian noted). Minstrel will take this into account
> when building the aggregate, but IIRC only for the first entry in the
> retry
Pete Heist writes:
>> On Jun 26, 2018, at 10:40 AM, Sebastian Moeller wrote:
>>
>> Hi Pete,
>>
>>> On Jun 26, 2018, at 00:40, Pete Heist wrote:
>>>
>>> The rrul test over a point-to-point WiFi link cuts the total TCP throughput
>>> considerably below that of rrul_be. For example, on an
> On Jun 26, 2018, at 10:40 AM, Sebastian Moeller wrote:
>
> Hi Pete,
>
>> On Jun 26, 2018, at 00:40, Pete Heist wrote:
>>
>> The rrul test over a point-to-point WiFi link cuts the total TCP throughput
>> considerably below that of rrul_be. For example, on an 802.11n 20MHz MCS 15
>> link:
Hi Pete,
> On Jun 26, 2018, at 00:40, Pete Heist wrote:
>
> The rrul test over a point-to-point WiFi link cuts the total TCP throughput
> considerably below that of rrul_be. For example, on an 802.11n 20MHz MCS 15
> link:
>
> rrul_be: ~90mbit
> rrul: ~30-45mbit
>
I believe this
The rrul test over a point-to-point WiFi link cuts the total TCP throughput
considerably below that of rrul_be. For example, on an 802.11n 20MHz MCS 15
link:
rrul_be: ~90mbit
rrul: ~30-45mbit
I think this came up before, but could the standard rrul test be exceeding the
802.11e spec in terms
