On 27 May 2013 14:22, Lev Serebryakov <l...@freebsd.org> wrote:
> Hello, Adrian.
> You wrote 28 мая 2013 г., 1:10:33:
> AC> Sweet. I think the problem getting n rates here are likely due to
> AC> buffer starvation when queuing the addba request or response frames.
> AC> So I still have to properly fix that. But it'll happen.

>   Cool! It is not show-stopper and could be due to noise environment.
>  We could not now for sure, is it bug or objective reality, that it
>  could not go faster :)

Well, there are still a lot of things to fix there. Right now if
frames are filtered due to the node going into power save, the driver
will treat them as a failed software retransmit. Too many of those
will equate to a dropped frame, and the TX is paused whilst the BAR is
sent out.

I bet I can fix that a bit. :-)

So I may end up being able to improve performance
>   Absence of n-ratets and, of course, de-associations WERE bugs, but I
>  could not repeat them anymore.

I still have to track down that and make sure those frames are
properly treated as a management queue frame in the ath(4) driver.

anyway, gotta catch a plane, bbl.

freebsd-wireless@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Reply via email to