From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Michael Yartys <michael.yartys@protonmail.com>
Cc: "make-wifi-fast\@lists.bufferbloat.net"
<make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] Higher latency on upload under poor signal conditions
Date: Tue, 16 Jun 2020 16:32:05 +0200 [thread overview]
Message-ID: <877dw7ytcq.fsf@toke.dk> (raw)
In-Reply-To: <o420hoTQgUTIYiKLb7MurfEtWgXyy0-A5PsMr0LG98llsSYPn3ZVEF39GJ3YekjXeIQAn7GUqeMnSU32GU6GmWSiTnlBtruHTeuWSZV_3vQ=@protonmail.com>
>> > Is this what I would be looking for (I only included the relevant part of the output)?
>> > $ iw wlp18s0 station dump
>> > tx packets: 742091
>> > tx retries: 417
>> > This is the output after running an upload test and getting pretty
>> > much the same results. I disabled and re-enabled the wireless NIC
>> > before the test since that seems to reset the stats. It doesn't really
>> > look like the retry rate is high, but I don't really know what's
>> > considered high in the first place.
>>
>> That does not seem overly high, no. I guess 80ms could just be queueing
>> delay, either in the firmware, or because your driver is not using
>> TXQs...
>
> It seems like I also have TXQs:
>
> $ iw phy | grep TXQ
> * [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
>
> I guess that it's probably in the firmware then. IIRC I don't see this
> behaviour when I have a good connection, but I'll have to perform a
> test to be sure.
Well, it may be that the firmware is doing a lot of retransmits and not
telling the OS. Or it may simply be that the poor connection ends up
dropping the effective rate so the buffering becomes more noticeable.
-Toke
next prev parent reply other threads:[~2020-06-16 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.581.1592302723.24343.make-wifi-fast@lists.bufferbloat.net>
2020-06-16 11:08 ` Sebastian Moeller
2020-06-16 11:35 ` Toke Høiland-Jørgensen
2020-06-16 11:50 ` Sebastian Moeller
2020-06-16 12:03 ` Toke Høiland-Jørgensen
2020-06-16 12:59 ` Michael Yartys
[not found] ` <fQ-GV16qlgI6k9RiyhVFGrDkwkMvGYE6iQTc4H6y7a4I-HXZ4ZVYRit74qPpcDg8UQQENbp7lZwinIZLyKg_hPx1EArregrBxVSUZR2XdIE=@protonmail.com>
2020-06-16 13:06 ` Toke Høiland-Jørgensen
2020-06-16 13:14 ` Michael Yartys
2020-06-16 14:32 ` Toke Høiland-Jørgensen [this message]
2020-06-30 18:22 ` Michael Yartys
2020-07-01 11:41 ` Toke Høiland-Jørgensen
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=877dw7ytcq.fsf@toke.dk \
--to=toke@redhat.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=michael.yartys@protonmail.com \
/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