From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Felix Fietkau <nbd@nbd.name>,
Rajkumar Manoharan <rmanohar@codeaurora.org>,
johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org, Kan Yan <kyan@google.com>
Subject: Re: [RFC v2] mac80211: budget outstanding airtime for transmission
Date: Fri, 21 Sep 2018 14:47:45 +0200 [thread overview]
Message-ID: <87r2hnhv9q.fsf@toke.dk> (raw)
In-Reply-To: <8d8e3775-4504-7b37-19b0-4a7fae054d12@nbd.name>
Felix Fietkau <nbd@nbd.name> writes:
> On 2018-09-20 21:05, Rajkumar Manoharan wrote:
>> Per frame airtime estimation could be used to track outstanding airtime
>> of each txq and can be used to throttle ieee80211_tx_dequeue(). This
>> mechanism on its own will get us the queue limiting and latency
>> reduction goodness for firmwares with deep queues. And for that it can
>> be completely independent of the airtime fairness scheduler, which can
>> use the after-tx-compl airtime information to presumably get more
>> accurate fairness which includes retransmissions etc.
> What about packets that get dequeued from the txq, but get freed by
> ieee80211_free_txskb?
> I think this may be a bit fragile, since if for any reason accounting
> isn't perfect here, tx queues might stall.
Yeah, I worry about that as well. I guess we basically have three
avenues for fixing this?
1. Make sure packets are not freed after dequeue (probably not
feasible).
2. Add a mechanism to get queues unstuck if accounting does deviate (a
watchdog-type thing, or tie it to packet enqueue or something?).
3. Tie this back into the airtime fairness scheduler deficit, the same
way Kan's original patch did.
The problem with (3) is that we lose the ability to use a different
source of airtime usage information for the fairness scheduler (without
doing weird subtractions in the accounting). In particular, this would
mean we can't account for retransmissions. So I'd prefer (2), I think.
Anyone else with bright ideas? :)
-Toke
next prev parent reply other threads:[~2018-09-21 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 19:05 [RFC v2] mac80211: budget outstanding airtime for transmission Rajkumar Manoharan
2018-09-21 11:13 ` Felix Fietkau
2018-09-21 12:47 ` Toke Høiland-Jørgensen [this message]
2018-09-21 14:11 ` Johannes Berg
2018-09-22 0:26 ` Rajkumar Manoharan
2018-09-22 0:53 ` Kan Yan
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=87r2hnhv9q.fsf@toke.dk \
--to=toke@toke.dk \
--cc=johannes@sipsolutions.net \
--cc=kyan@google.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=rmanohar@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).