Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Oleksij Rempel <linux@rempel-privat.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Stable Version for ath9k_htc in AP Mode?
Date: Tue, 06 May 2014 09:21:25 +0200	[thread overview]
Message-ID: <53688D75.9040006@rempel-privat.de> (raw)
In-Reply-To: <CAFjWW+YaXtyq5qZTex9YW=NWLovfBgrNO9v_WFywbddD7di4uQ@mail.gmail.com>

Am 06.05.2014 03:57, schrieb Aaron Hamilton:
> Oh ok. Is this not already handled by hostapd or the wifi drivers?

No. hostapd suggest which rutaes should be used and driver, btw.
mac80211 should fallow this suggestion. ip layer is not touched.

> 
> Also, I reverted back to backports-3.12.8-1 and now trying to see if
> there's a difference when using sch_codel.ko and sch_fq_codel.ko
> (previously these two modules were not used as I was trying to minimize
> the number of moving parts). Which by the way, am I gaining or loosing
> anything with these? I'm not quiet sure what their purpose is.

Scheduling is good for many reasons. For example, if you know what
bandwidth you have (in your case you know it) it is possible to use
priority for critical applications. DNS and ICMP traffic will have
higher priority then HTTP, and so on. Read more about QoS.
I would suggest to set scheduler to bandwidth lover then your USB
bandwidth. It should reduces usage of ath9k_htc_fw buffer. If you
configure scheduler, please try remove "supported_rates=10 20 55" from
you config.

Don't forget. It is not enough to add scheduler module. You will need
configure it.

> I'm also using the attached hostapd.conf file. Previously, when two
> devices were on the WiFi, one would always have ping latency of several
> hundred milliseconds despite minimal traffic on either host. Now latency
> only seems to spike when a large continuous file is moved across the
> WiFi. Streaming of music for example doesn't seem to have much effect on
> the other WiFi clients.

How about filed tests? Do you still have stability issues?

> # Begin hosatpd.conf
> interface=wlan0
> driver=nl80211
> 
> hw_mode=g
> 
> dump_file=/tmp/hostapd.dump
> ctrl_interface=/var/run/hostapd
> ctrl_interface_group=0
> 
> logger_syslog=-1
> logger_syslog_level=2
> beacon_int=500
> dtim_period=2
> 
> supported_rates=10 20 55
> 
> max_num_sta=5
> rts_threshold=2347
> fragm_threshold=2346
> 
> macaddr_acl=0
> eapol_version=1
> eapol_key_index_workaround=0
> 
> # Attempting max time-outs for increased reliability
> wpa_group_rekey=0
> wpa_gmk_rekey=86400
> # wmm_enabled=1
> ieee80211n=1
> ieee80211d=1
> country_code=DE
> ht_capab=[HT40+][RX-STBC1][DSSS_CCK-40][SHORT-GI-40]
> ignore_broadcast_ssid=0
> channel=1
> ssid=TestSSID
> 
> auth_algs=1
> wpa=2
> wpa_key_mgmt=WPA-PSK
> 
> wpa_pairwise=CCMP
> rsn_pairwise=CCMP
> 
> wpa_passphrase=fixmeplease
> # end hostapd.conf
> 
> 
> On Mon, May 5, 2014 at 12:32 PM, Oleksij Rempel <linux@rempel-privat.de
> <mailto:linux@rempel-privat.de>> wrote:
> 
>     Am 05.05.2014 20:09, schrieb Aaron Hamilton:
>     > I'm sorry, what's TC?
> 
>     http://linux.die.net/man/8/tc
> 
>     > On Sat, May 3, 2014 at 2:07 AM, Oleksij Rempel
>     <linux at rempel-privat.de <mailto:linux@rempel-privat.de>
>     > <mailto:linux at rempel-privat.de <mailto:linux@rempel-privat.de>>>
>     wrote:
>     >
>     >     Am 02.05.2014 12:11, schrieb Aaron Hamilton:
>     >     > Ok, I updated the drivers to backports 3.14-1 and configured the
>     >     > following hostapd settings. I connected an iPad and a
>     Windows PC, then
>     >     > ran continuous pings. For the first couple seconds
>     everything was
>     >     > returning in a few milliseconds. Within 30 seconds, the
>     pings started
>     >     > getting into the several hundred ms range (or timing out)
>     and remained
>     >     > there (for both the iPad and PC).
>     >     >
>     >     > After I disconnected the PC from the WiFi, the iPad's pings
>     dropped to
>     >     > an average of 15ms (about 30s to a minute after the PC was
>     moved to
>     >     > another AP).
> 
>     --
>     Regards,
>     Oleksij
> 
> 


-- 
Regards,
Oleksij

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 278 bytes
Desc: OpenPGP digital signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20140506/9466fef2/attachment.pgp 

  reply	other threads:[~2014-05-06  7:21 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28 20:43 [ath9k-devel] Stable Version for ath9k_htc in AP Mode? Aaron Hamilton
2014-04-28 22:03 ` Oleksij Rempel
2014-04-29  6:19   ` Aaron Hamilton
2014-04-29  6:31     ` Oleksij Rempel
2014-04-29  9:08       ` Aaron Hamilton
2014-04-30 17:29         ` Aaron Hamilton
2014-04-30 18:27           ` Oleksij Rempel
2014-04-30 18:59             ` Aaron Hamilton
2014-04-30 20:16               ` Oleksij Rempel
2014-04-30 20:40                 ` Oleksij Rempel
2014-04-30 23:03                   ` Aaron Hamilton
2014-05-01  5:37                     ` Oleksij Rempel
2014-05-01 21:33                       ` Aaron Hamilton
2014-05-01 22:00                       ` Aaron Hamilton
2014-05-01 22:41                         ` Oleksij Rempel
2014-05-02  6:27                           ` Aaron Hamilton
2014-05-02 10:11                             ` Aaron Hamilton
2014-05-03  9:07                               ` Oleksij Rempel
2014-05-05 18:09                                 ` Aaron Hamilton
2014-05-05 19:32                                   ` Oleksij Rempel
2014-05-06  1:57                                     ` Aaron Hamilton
2014-05-06  7:21                                       ` Oleksij Rempel [this message]
2014-05-08 22:57                                         ` Aaron Hamilton
2014-05-10  9:26                                           ` Oleksij Rempel
2014-05-11  6:40                                             ` Aaron Hamilton
2014-05-11 15:40                                               ` Adrian Chadd
2014-05-12  1:46                                                 ` Aaron Hamilton
2014-05-12  8:01                                                   ` Oleksij Rempel
2014-05-12 13:11                                                     ` Peter Stuge
2014-05-12 14:47                                                       ` Oleksij Rempel
2014-05-28  5:36                                                         ` Aaron Hamilton
2014-05-30  4:21                                                           ` Oleksij Rempel
2014-06-04 18:06                                                             ` Aaron Hamilton
2014-06-06  2:12                                                               ` Aaron Hamilton
2014-06-06  7:52                                                                 ` Oleksij Rempel
2014-06-06 11:06                                                                   ` Aaron Hamilton
2014-06-06 20:24                                                                     ` Gui Iribarren
2014-06-06 20:27                                                                     ` Gui Iribarren
2014-05-01  4:12               ` Ben Greear

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=53688D75.9040006@rempel-privat.de \
    --to=linux@rempel-privat.de \
    --cc=ath9k-devel@lists.ath9k.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