From: Pete Heist <peteheist@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] [PATCH v2] iw: Print TXQ statistics for stations and interfaces
Date: Thu, 22 Feb 2018 13:10:35 +0100 [thread overview]
Message-ID: <431766C8-135F-4A69-85DA-784A1D2C4ED0@gmail.com> (raw)
In-Reply-To: <20180222101848.18772-1-toke@toke.dk>
> On Feb 22, 2018, at 11:18 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Sample output:
>
> $ iw dev wlp2s0 station dump -v
> Station xx:xx:xx:xx:xx:xx (on wlp2s0)
> [...]
> TXQs:
> TID qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
> 0 0 0 0 0 0 0 0 0 0
> 1 0 0 0 0 0 0 0 0 0
> 2 0 0 0 0 0 0 0 0 0
> 3 0 0 0 0 0 0 0 0 0
> 4 0 0 0 0 0 0 0 0 0
> 5 0 0 0 0 0 0 0 0 0
> 6 0 0 0 0 0 0 0 0 0
> 7 0 0 0 0 0 0 0 0 0
> 8 0 0 0 0 0 0 0 0 0
> 9 0 0 0 0 0 0 0 0 0
> 10 0 0 0 0 0 0 0 0 0
> 11 0 0 0 0 0 0 0 0 0
> 12 0 0 0 0 0 0 0 0 0
> 13 0 0 0 0 0 0 0 0 0
> 14 0 0 0 0 0 0 0 0 0
> 15 0 0 0 0 0 0 0 0 0
> [...]
>
> $ iw dev wlp2s0 info
> Interface wlp2s0
> ifindex 9
> wdev 0x1
> addr xx:xx:xx:xx:xx:xx
> type AP
> wiphy 0
> channel 165 (5825 MHz), width: 20 MHz, center1: 5825 MHz
> txpower 24.00 dBm
> multicast TXQ:
> qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
> 0 0 72 0 0 0 0 7380 72
>
Could these stats make possible a userspace tool for determining the proportion of delay that is introduced by congestion vs by link layer issues? Such a tool could be really helpful for network engineers wanting to mitigate delay issues and not sure where to best focus their efforts...
Pete
next prev parent reply other threads:[~2018-02-22 12:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 17:02 [Make-wifi-fast] [PATCH 0/3] Export TXQ parameters and statistics via nl80211 Toke Høiland-Jørgensen
2018-02-19 17:02 ` [Make-wifi-fast] [PATCH 1/3] cfg80211: Expose TXQ stats and parameters to userspace Toke Høiland-Jørgensen
2018-05-07 19:13 ` Johannes Berg
2018-05-07 21:19 ` Toke Høiland-Jørgensen
2018-05-07 21:20 ` Johannes Berg
2018-05-08 10:18 ` Toke Høiland-Jørgensen
2018-05-08 10:18 ` Johannes Berg
2018-05-08 10:19 ` Johannes Berg
2018-05-08 10:23 ` Toke Høiland-Jørgensen
2018-05-08 10:21 ` Johannes Berg
2018-02-19 17:02 ` [Make-wifi-fast] [PATCH 2/3] iw: Print TXQ statistics for stations and interfaces Toke Høiland-Jørgensen
2018-05-07 21:21 ` Johannes Berg
2018-05-07 21:30 ` Toke Høiland-Jørgensen
2018-02-19 17:02 ` [Make-wifi-fast] [PATCH 3/3] iw: Add getting and setting of TXQ params for phy Toke Høiland-Jørgensen
2018-02-21 8:56 ` [Make-wifi-fast] [PATCH 0/3] Export TXQ parameters and statistics via nl80211 Arend van Spriel
2018-02-21 11:00 ` Toke Høiland-Jørgensen
2018-02-21 19:53 ` Arend van Spriel
2018-02-22 10:11 ` Toke Høiland-Jørgensen
2018-02-22 10:18 ` [Make-wifi-fast] [PATCH v2] iw: Print TXQ statistics for stations and interfaces Toke Høiland-Jørgensen
2018-02-22 12:10 ` Pete Heist [this message]
2018-02-22 12:32 ` Toke Høiland-Jørgensen
2018-04-19 9:20 ` [Make-wifi-fast] [PATCH 0/3] Export TXQ parameters and statistics via nl80211 Toke Høiland-Jørgensen
2018-04-19 9:52 ` Johannes Berg
2018-04-19 10:30 ` 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=431766C8-135F-4A69-85DA-784A1D2C4ED0@gmail.com \
--to=peteheist@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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