Hi Oleksij,
---
--- a /drivers/net/wireless/ath/ath9k/hif_usb.h
+++ b/drivers/net/wireless/ath/ath9k/hif_usb.h
@@ -34,7 +34,10 @@
/* FIXME: Verify these numbers (with Windows) */
#define MAX_TX_URB_NUM 8
-#define MAX_TX_BUF_NUM 256
+/* Decrease BUF_NUM to have the same values for
+ * TX_THRESHOLD in driver and HTC_MAX_TX_STATUS
+ * in firmware. This reduce load on the Adapter */
+#define MAX_TX_BUF_NUM 22
#define MAX_TX_BUF_SIZE 32768
#define MAX_TX_AGGR_NUM 20
--
With...
#define ATH9K_HTC_TX_RESERVE 10
#define ATH9K_HTC_TX_THRESHOLD (MAX_TX_BUF_NUM - ATH9K_HTC_TX_RESERVE)
... this Patch decreases the ATH9K_HTC_TX_THRESHOLD to 12, so that the queue
has never more than 12 items.
Therefore the cnt for tx_status in the firmware never gets over
HTC_MAX_TX_STATUS (defined as 12).
Regards,
Lukas
Am 23.12.2015 um 12:50 schrieb Oleksij Rempel:
> Hi,
>
> thank you for your testing.
>
> Am 23.12.2015 um 11:53 schrieb Lukas Göstl:
> > Hi again,
> >
> > I got my Mesh Network running without any of the wireless adapters
> > getting stuck. The Problem was that the adapter got overwhelmed when
> > the ath9k driver wanted to send more packets than the adapter could
> process. More precisely the adapter got Problems when the
> HTC_MAX_TX_STATUS (defined as 12) was reached. So I reduced the
> software queue of the ath9k driver from 256 to 12 Packets.
>
> I'm not sure what you mean. Please send diff with your changes.
>
> > However the performance could be better. Has anyone an idea for another
> solution or a suggestion to increase the performance?
> >
> > Thanks,
> > Lukas
> >
> >> Hi all,
> >>
> >> i successfully build up a secure Mesh Network over 20 Nodes with
> >> wpa_supplicant, ath9k_htc and linux-kernel 3.18
> >>
> >> I know there is a limit of station peering's on ath9k_htc, however I
> whitelisted the stations in a way, that only 7 Peers authenticate with each
> other.
> >>
> >> The Mesh Network runs well for about 2 - 3 hours. Then some wireless
> adapters get stuck and do not response anymore. They need a Powercycle to
> work again.
> >>
> >> Has anybody an idea why this happens or what`s the best way to debug
> such a problem? I don't get any output in syslog.
> >>
> >> Thanks,
> >> Lukas
> > _______________________________________________
> > ath9k-devel mailing list
> > ath9k-devel@lists.ath9k.org
> > https://lists.ath9k.org/mailman/listinfo/ath9k-devel
> >
>
>
> --
> Regards,
> Oleksij
_______________________________________________
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
