From: bkil <bkil.hu+Aq@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] tcp_pacing_rate_shift and smaller txops
Date: Mon, 2 Jul 2018 22:12:05 +0200 [thread overview]
Message-ID: <CAPuHQ=HMREdgQXYP8MrhmvwJmvQ4hf6Zzs1_YGKEMrkk1_x=Gw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5WH4KQcqm2vv1Zag-s25xO-UyYN5CLBcf1q=nzwmVzvg@mail.gmail.com>
Interesting observation. Do you think the new wmm rules could prevent
fine tuning of these constants later on?
https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/commit/?id=fde57be08890095132b9f7d28aaaf9a026b2e608
On Mon, Jul 2, 2018 at 9:44 PM, Dave Taht <dave.taht@gmail.com> wrote:
> wifi APs have the ability to advertise in the beacon, the actual
> maximum time of a txop for clients, and 802.11n, for example, cannot
> queue an aggregate in the VO queue. the otherwise lovely
> tcp_pacing_rate shift thing sets this to a fixed 4ms, when perhaps it
> could leverage the actual setting for the queue in question, at least,
> as defined by the beacon or 802.11e standard.
>
> I've long thought that perhaps a gaming wifi router would advertise
> smaller txops, and for all I know, some do.
>
> this is currently controlled by cwmin and cwmax parameters in hostapd
>
> # Best effort
> #tx_queue_data2_aifs=3
> #tx_queue_data2_cwmin=15
> #tx_queue_data2_cwmax=63
> #tx_queue_data2_burst=0
>
> I did a lot of fiddling with this (lowering it to 1,1.5,2ms,3ms,4ms)
> at one point (that I cannot currently find). It hurt bandwidth but
> helped latency, a lot, and this was from before we shipped fq_codel
> for wifi.
>
> --
>
> Dave Täht
> CEO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-669-226-2619
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
prev parent reply other threads:[~2018-07-02 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 19:44 Dave Taht
2018-07-02 20:12 ` bkil [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPuHQ=HMREdgQXYP8MrhmvwJmvQ4hf6Zzs1_YGKEMrkk1_x=Gw@mail.gmail.com' \
--to=bkil.hu+aq@gmail.com \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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