From: Justin Capella <justincapella@gmail.com>
To: Yibo Zhao <yiboz@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, ath10k <ath10k@lists.infradead.org>
Subject: Re: [PATCH V4 0/4] Enable virtual time-based airtime scheduler support on ath10k
Date: Fri, 13 Dec 2019 01:03:41 -0800 [thread overview]
Message-ID: <CAMrEMU_w7dj5RVNmkVoCjU1o_FEEXn9oA7XCBwFQ+j2EQkck4Q@mail.gmail.com> (raw)
In-Reply-To: <1576221593-1086-1-git-send-email-yiboz@codeaurora.org>
Would it make sense to consider skb->priority / QoS in the Access
Classifier selection?
On Thu, Dec 12, 2019 at 11:26 PM Yibo Zhao <yiboz@codeaurora.org> wrote:
>
> This series fix some issues when enabling virtual time-based airtime scheduler on ath10k.
>
> Changes since v3:
> Change schedule_pos to previous node once it has chance to be moved/removed
> from current position in the tree in loop scenario and bring back schedule_round
> in case that same node is to be scheduled again in the mean time.
>
> Increase airtime grace period to 2000 us in the first patch.
>
> Put per-AC station weight checking in its lock during configuration from application.
>
> Changes since v2:
> Changes station airtime weight to be per-AC based to avoid sync issue
> Remove Co-developed-by and Toke's sign-off as Toke suggested
>
> Changes since v1:
> Modify the author of Co-developed-by as Johannes suggested
>
> Toke Høiland-Jørgensen (1):
> mac80211: Switch to a virtual time-based airtime scheduler
>
> Yibo Zhao (3):
> mac80211: fix issue in loop scenario
> mac80211: fix low throughput in multi-clients situation
> mac80211: Sync airtime weight sum with per AC synced sta airtime
> weight together
>
> net/mac80211/cfg.c | 29 +++++-
> net/mac80211/debugfs.c | 48 +++++++++-
> net/mac80211/debugfs_sta.c | 18 ++--
> net/mac80211/ieee80211_i.h | 12 ++-
> net/mac80211/main.c | 2 +-
> net/mac80211/sta_info.c | 25 +++--
> net/mac80211/sta_info.h | 8 +-
> net/mac80211/tx.c | 234 +++++++++++++++++++++++++++++++--------------
> 8 files changed, 278 insertions(+), 98 deletions(-)
>
> --
> 1.9.1
next prev parent reply other threads:[~2019-12-13 9:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 7:19 [PATCH V4 0/4] Enable virtual time-based airtime scheduler support on ath10k Yibo Zhao
2019-12-13 7:19 ` [PATCH 1/4] mac80211: Switch to a virtual time-based airtime scheduler Yibo Zhao
2019-12-13 7:19 ` [PATCH 2/4] mac80211: fix issue in loop scenario Yibo Zhao
2019-12-13 9:56 ` Johannes Berg
2019-12-18 10:12 ` yiboz
2019-12-18 10:18 ` Johannes Berg
2019-12-18 10:37 ` Toke Høiland-Jørgensen
2019-12-13 7:19 ` [PATCH 3/4] mac80211: fix low throughput in multi-clients situation Yibo Zhao
2020-01-08 10:46 ` Justin Capella
2020-01-08 11:31 ` Toke Høiland-Jørgensen
2019-12-13 7:19 ` [PATCH 4/4] mac80211: Sync airtime weight sum with per AC synced sta airtime weight together Yibo Zhao
2019-12-13 9:58 ` Johannes Berg
2019-12-17 15:20 ` Toke Høiland-Jørgensen
2019-12-13 9:03 ` Justin Capella [this message]
2019-12-13 10:06 ` [PATCH V4 0/4] Enable virtual time-based airtime scheduler support on ath10k 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=CAMrEMU_w7dj5RVNmkVoCjU1o_FEEXn9oA7XCBwFQ+j2EQkck4Q@mail.gmail.com \
--to=justincapella@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=yiboz@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).