From: Bob Copeland <me@bobcopeland.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: Dave Taht <dave.taht@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Felix Fietkau <nbd@openwrt.org>, Tim Shepard <shep@alum.mit.edu>
Subject: Re: [RFC/RFT] mac80211: implement fq_codel for software queuing
Date: Tue, 8 Mar 2016 08:14:09 -0500 [thread overview]
Message-ID: <20160308131409.GD5026@localhost> (raw)
In-Reply-To: <CA+BoTQk+3jhwK57_fDw0scNCGzu_Edqp9-Beeppz8xj9kSQcoQ@mail.gmail.com>
On Tue, Mar 08, 2016 at 08:12:21AM +0100, Michal Kazior wrote:
> However other drivers (e.g. ath10k) have offloaded rate control on
> device. There's currently no way of doing this calculation. I was
> thinking of drivers exporting tx_rate to mac80211 in some way - either
> via a simple sta->tx_rate scalar that the driver is responsible for
> updating, or a EWMA that driver updates (hopefully) periodically and
> often enough. This should in theory at least allow an estimate how
> much data on average you can fit into given time frame (e.g. txop, or
> hardcoded 1ms).
What about implementing ops->get_expected_throughput? This would be
useful for mesh (both 11s and batman) as well since they need to
estimate link quality to pick a path.
--
Bob Copeland %% http://bobcopeland.com/
next prev parent reply other threads:[~2016-03-08 13:14 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 13:09 [RFC/RFT] mac80211: implement fq_codel for software queuing Michal Kazior
2016-02-26 16:48 ` Felix Fietkau
2016-02-26 16:48 ` Felix Fietkau
2016-02-26 18:54 ` Michal Kazior
2016-03-01 14:02 ` Johannes Berg
2016-03-02 7:38 ` Michal Kazior
2016-03-03 17:00 ` Dave Taht
2016-03-03 17:00 ` Dave Taht
2016-03-04 2:48 ` Tim Shepard
2016-03-04 6:32 ` Michal Kazior
2016-03-07 14:05 ` Avery Pennarun
2016-03-07 14:05 ` Avery Pennarun
2016-03-07 15:09 ` Felix Fietkau
2016-03-07 15:09 ` Felix Fietkau
2016-03-07 16:25 ` Avery Pennarun
2016-03-07 16:25 ` Avery Pennarun
2016-03-07 16:54 ` Dave Taht
2016-03-07 16:54 ` Dave Taht
2016-03-07 17:14 ` Avery Pennarun
2016-03-07 17:14 ` Avery Pennarun
2016-03-07 17:22 ` Grumbach, Emmanuel
2016-03-07 17:22 ` Grumbach, Emmanuel
2016-03-07 18:28 ` Dave Taht
2016-03-08 7:41 ` Michal Kazior
2016-03-08 7:41 ` Michal Kazior
2016-03-07 23:06 ` Dave Taht
2016-03-07 23:06 ` Dave Taht
2016-03-08 7:12 ` Michal Kazior
2016-03-08 10:19 ` Toke Høiland-Jørgensen
2016-03-08 13:14 ` Bob Copeland [this message]
2016-03-08 13:27 ` Michal Kazior
2016-03-10 18:57 ` Dave Taht
2016-03-10 18:57 ` Dave Taht
2016-03-11 8:32 ` Michal Kazior
2016-03-08 10:57 ` Michal Kazior
2016-03-08 10:57 ` Michal Kazior
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=20160308131409.GD5026@localhost \
--to=me@bobcopeland.com \
--cc=dave.taht@gmail.com \
--cc=emmanuel.grumbach@intel.com \
--cc=eric.dumazet@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.com \
--cc=nbd@openwrt.org \
--cc=netdev@vger.kernel.org \
--cc=shep@alum.mit.edu \
/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.