All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	make-wifi-fast@lists.bufferbloat.net,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/3] Export TXQ parameters and statistics via nl80211
Date: Wed, 21 Feb 2018 20:53:31 +0100	[thread overview]
Message-ID: <5A8DCE3B.3000607@broadcom.com> (raw)
In-Reply-To: <87bmgiboan.fsf@toke.dk>

On 2/21/2018 12:00 PM, Toke Høiland-Jørgensen wrote:
> Arend van Spriel <arend.vanspriel@broadcom.com> writes:
>
>> On 2/19/2018 6:02 PM, Toke Høiland-Jørgensen wrote:
>>> This series adds TXQ parameters and statistics that were previously only
>>> available through debugfs to the nl80211 userspace interface and the
>>> cfg80211 kernel interface. Patches for iw to print the statistics and
>>> change the settings are included.
>>
>> So what is your motivation for having this exposed through nl80211.
>> For the average end-user the stats and parameters are fairly fuzzy.
>
> Two reasons, basically:
>
> 1. Visibility and statistics; this is basically the same information
>     that is available at the qdisc layer (with `tc -s qdisc`), but which
>     has been missing on WiFi interfaces ever sine we switched to the TXQ
>     structure. Having this available has been quite valuable for
>     debugging qdisc setups on wired links, and it's not always feasible
>     to ask users to recompile their kernels with debugfs enabled.
>
> 2. Having visibility into the queues from userspace makes it possible to
>     make decisions based upon (e.g.) which stations are currently
>     backlogged. I'm working on a "policy mode" for the airtime fairness
>     scheduler which will use this capability.

I see. Was just wondering whether there were concrete user-space 
applications planned to use the information. Cool.

>> So can we expect some manual in which is described what parameter
>> should be tweaked based on the retrieved statistics.
>
> Heh, not sure I'll promise a whole manual, but I am happy to write a
> blog post (or wiki page if that's better) explaining what these values
> mean and what insight one might gain from them.

My preference would be to have something on wireless.wiki.kernel.org. 
Another option might be to add kerneldoc section for this.

Regards,
Arend

  reply	other threads:[~2018-02-21 19:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 17:02 [PATCH 0/3] Export TXQ parameters and statistics via nl80211 Toke Høiland-Jørgensen
2018-02-19 17:02 ` [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 ` [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 ` [PATCH 3/3] iw: Add getting and setting of TXQ params for phy Toke Høiland-Jørgensen
2018-02-21  8:56 ` [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 [this message]
2018-02-22 10:11       ` Toke Høiland-Jørgensen
2018-02-22 10:18 ` [PATCH v2] iw: Print TXQ statistics for stations and interfaces Toke Høiland-Jørgensen
2018-04-19  9:20 ` [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5A8DCE3B.3000607@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.