On Mon, Sep 15, 2008 at 5:04 PM, Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx> wrote: > On Mon, Sep 15, 2008 at 4:24 PM, Luis R. Rodriguez > <lrodriguez@xxxxxxxxxxx> wrote: > > So the problem with ath9k is we report only 1 ampdu queue and when we > try to map tid 6 to a queue we cannot do it as we already have one for > tid 0 with the ap. > > [ 9653.596135] Open BA session requested for 00:03:7f:0c:e0:bc tid 6 > [ 9653.596146] BA request denied - queue unavailable for tid 6 > [ 9653.688091] Open BA session requested for 00:03:7f:0c:e0:bc tid 6 > [ 9653.688095] BA request denied - queue unavailable for tid 6 > > If I up the "ampdu" queues to >= 2 on ath9k I then am able to allocate > more TID sessions to more "ampdu queues". But my results are pretty > horrible: > > [ 5] local 192.168.1.5 port 5001 connected with 192.168.1.11 port 52651 > [ 5] 0.0- 1.0 sec 1.99 MBytes 16.7 Mbits/sec > [ 5] 1.0- 2.0 sec 2.63 MBytes 22.0 Mbits/sec > [ 5] 2.0- 3.0 sec 1.26 MBytes 10.6 Mbits/sec > [ 5] 3.0- 4.0 sec 740 KBytes 6.06 Mbits/sec > [ 5] 4.0- 5.0 sec 1.48 MBytes 12.4 Mbits/sec > [ 5] 5.0- 6.0 sec 1.57 MBytes 13.2 Mbits/sec > [ 5] 6.0- 7.0 sec 2.78 MBytes 23.3 Mbits/sec > [ 5] 7.0- 8.0 sec 250 KBytes 2.05 Mbits/sec > [ 5] 8.0- 9.0 sec 2.00 MBytes 16.8 Mbits/sec > [ 5] 9.0-10.0 sec 1.80 MBytes 15.1 Mbits/sec > [ 5] 0.0-10.4 sec 16.7 MBytes 13.5 Mbits/sec > > Something is up... With AR9280 I get better results, yet fishy. [ 4] local 192.168.1.5 port 5001 connected with 192.168.1.13 port 36835 [ 4] 0.0- 1.0 sec 3.58 MBytes 30.0 Mbits/sec [ 4] 1.0- 2.0 sec 4.76 MBytes 39.9 Mbits/sec [ 4] 2.0- 3.0 sec 5.62 MBytes 47.2 Mbits/sec [ 4] 3.0- 4.0 sec 7.27 MBytes 60.9 Mbits/sec [ 4] 4.0- 5.0 sec 5.65 MBytes 47.4 Mbits/sec [ 4] 5.0- 6.0 sec 7.10 MBytes 59.6 Mbits/sec [ 4] 6.0- 7.0 sec 4.63 MBytes 38.9 Mbits/sec [ 4] 7.0- 8.0 sec 6.20 MBytes 52.0 Mbits/sec [ 4] 8.0- 9.0 sec 4.54 MBytes 38.1 Mbits/sec [ 4] 9.0-10.0 sec 6.64 MBytes 55.7 Mbits/sec [ 4] 0.0-10.2 sec 56.7 MBytes 46.6 Mbits/sec Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
