All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Ivo Van Doorn <ivdoorn@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: Rate control & USB
Date: Mon, 12 Jul 2010 17:17:51 +0200	[thread overview]
Message-ID: <4C3B321F.2020609@openwrt.org> (raw)
In-Reply-To: <AANLkTinubmjYu9FyDU0B81F0gHmFPLnDUWYGmZ9Rodss@mail.gmail.com>

On 2010-07-12 12:48 PM, Ivo Van Doorn wrote:
> The problem here is that we have lost the per-sta statistics. However using the
> single TX status reports, we can count the number of frames which are sent for
> a given STA during the poll interval. We can then determine the percentage of
> frames sent for that STA, We can then add the percentage of the retry and ACK
> count to each STA. Throughout poll interval the rate algorithm would send all
> frames to the same STA with the same TX rate, but between polls, the rate will
> be updated.
> 
> Overall these changes will not make the optimal use of PID or
> Minstrel, but it would
> at least improve the situation for USB.
> 
> Any thoughts about this solution?
I don't know how minstrel could work with this approach. Before it
starts to use a rate, it has to sample it first. How can you sample
rates with your tx status feedback approach?

- Felix

  reply	other threads:[~2010-07-12 15:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-12 10:48 Rate control & USB Ivo Van Doorn
2010-07-12 15:17 ` Felix Fietkau [this message]
2010-07-12 15:20   ` John W. Linville
2010-07-12 18:55     ` Ivo Van Doorn
2010-07-12 16:25 ` Steve deRosier
2010-07-12 18:54   ` Ivo Van Doorn
2010-07-12 19:14 ` Helmut Schaa
2010-07-13  6:59   ` Ivo Van Doorn
2010-07-13 19:15     ` Helmut Schaa
2010-07-13 19:51       ` Ivo Van Doorn
2010-07-14  1:53         ` Julian Calaby
2010-07-14 21:36           ` Ivo Van Doorn

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=4C3B321F.2020609@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=ivdoorn@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /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.