From: Luca Muscariello <luca.muscariello@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"make-wifi-fast@lists.bufferbloat.net"
<make-wifi-fast@lists.bufferbloat.net>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
Subject: Re: [Make-wifi-fast] [RFC/RFT 0/5] Adding an airtime fairness scheduler to ath9k
Date: Sun, 5 Jun 2016 13:40:37 +0200 [thread overview]
Message-ID: <CAHx=1M7SFK_zCeeM12U+W4OihRoPG8Ln3juZMhq3Ei4P6rNf=g@mail.gmail.com> (raw)
In-Reply-To: <877fe3ucvl.fsf@toke.dk>
[-- Attachment #1: Type: text/plain, Size: 1552 bytes --]
On Sunday, 5 June 2016, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Luca Muscariello <luca.muscariello@gmail.com <javascript:;>> writes:
>
> > I don't fully understand your plots but it would be useful to report
> > the physical rate of the stations.
>
> Yes, well, there's not really one rate to report for each station, since
> Minstrel jumps about a bit and tries different ones.
>
>
I know. Try a simple case, one STA very close one far away. I am able to
get quite stable average PHY rates with minstrel. 5GHz and a free
channel can also help to get low variance in your numbers. A Faraday cage
can also help :) .
> > As a benchmark, if you know the physical rates assuming they are also
> > optimally chosen (by minstrel for instance ) and stations don't move,
> > the long term throughout can be computed ( e.g. for TCP ) assuming air
> > time fairness. Than you can understand if your gain is what you should
> > expect or if the implementation is not yet done.
>
> So far I've just been looking at the figures for airtime (the first
> graph in the blog post). These are the same numbers that the scheduler
> uses to make scheduling decisions. It seems like the scheduler does help
> somewhat, but is not perfect yet. Am definitely lacking a good ground
> truth to compare against, though. Computing the expected throughput
> might be possible, since minstrel does report statistics for how many
> packets were transmitted at each rate. Will look into it; thanks for the
> suggestion :)
>
> -Toke
>
[-- Attachment #2: Type: text/html, Size: 2068 bytes --]
prev parent reply other threads:[~2016-06-05 11:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 16:51 Toke Høiland-Jørgensen
2016-06-03 16:51 ` [Make-wifi-fast] [RFC/RFT 1/5] mac80211: skip netdev queue control with software queuing Toke Høiland-Jørgensen
2016-06-06 2:26 ` Julian Calaby
2016-06-06 17:00 ` Toke Høiland-Jørgensen
2016-06-03 16:51 ` [Make-wifi-fast] [RFC/RFT 2/5] ath9k: use mac80211 intermediate software queues Toke Høiland-Jørgensen
2016-06-03 16:51 ` [Make-wifi-fast] [RFC/RFT 3/5] ath9k: Add airstame stats to per-station debugfs Toke Høiland-Jørgensen
2016-06-03 16:51 ` [Make-wifi-fast] [RFC/RFT 4/5] ath9k: Add a per-station airtime deficit scheduler Toke Høiland-Jørgensen
2016-06-03 16:51 ` [Make-wifi-fast] [RFC/RFT 5/5] ath9k: Count RX airtime in airtime deficit Toke Høiland-Jørgensen
2016-06-04 17:06 ` Adrian Chadd
2016-06-05 10:55 ` Toke Høiland-Jørgensen
2016-06-05 17:23 ` Adrian Chadd
2016-06-07 0:01 ` Adrian Chadd
2016-06-07 1:31 ` Jonathan Morton
2016-06-07 8:58 ` Toke Høiland-Jørgensen
2016-06-07 11:12 ` Toke Høiland-Jørgensen
2016-06-08 1:41 ` Adrian Chadd
2016-06-08 13:06 ` Toke Høiland-Jørgensen
2016-06-10 8:40 ` Michal Kazior
2016-06-10 8:53 ` Toke Høiland-Jørgensen
2016-06-10 9:02 ` Michal Kazior
2016-06-10 9:08 ` Toke Høiland-Jørgensen
2016-06-10 9:20 ` Michal Kazior
2016-06-10 9:49 ` Toke Høiland-Jørgensen
2016-06-10 15:33 ` Toke Høiland-Jørgensen
2016-06-10 15:52 ` Adrian Chadd
2016-06-04 15:24 ` [Make-wifi-fast] [RFC/RFT 0/5] Adding an airtime fairness scheduler to ath9k Luca Muscariello
2016-06-05 10:51 ` Toke Høiland-Jørgensen
2016-06-05 11:40 ` Luca Muscariello [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='CAHx=1M7SFK_zCeeM12U+W4OihRoPG8Ln3juZMhq3Ei4P6rNf=g@mail.gmail.com' \
--to=luca.muscariello@gmail.com \
--cc=ath9k-devel@lists.ath9k.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox