From: Baligh Gasmi <gasmibal@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Baligh Gasmi <gasmibal@gmail.com>
Subject: [RFC PATCH v4 0/3] expected throughput from AQL airtime
Date: Wed, 1 Jun 2022 13:29:00 +0200 [thread overview]
Message-ID: <20220601112903.2346319-1-gasmibal@gmail.com> (raw)
v4:
- Fix compilation error
- Take into acount channel busy time
v3:
- Update to new MLO sta struct
v2:
- Total size overflow, use u64 instead of u32
v1:
- Make one div after at least 100ms rather than one div each skb
Baligh Gasmi (3):
mac80211: use AQL airtime for expected throughput.
mac80211: add periodic monitor for channel busy time
mac80211: add busy time factor into expected throughput
net/mac80211/driver-ops.h | 2 ++
net/mac80211/ieee80211_i.h | 6 ++++
net/mac80211/iface.c | 65 ++++++++++++++++++++++++++++++++++++++
net/mac80211/sta_info.c | 46 +++++++++++++++++++++++++++
net/mac80211/sta_info.h | 11 +++++++
net/mac80211/status.c | 2 ++
net/mac80211/tx.c | 8 ++++-
7 files changed, 139 insertions(+), 1 deletion(-)
--
2.36.1
next reply other threads:[~2022-06-01 11:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 11:29 Baligh Gasmi [this message]
2022-06-01 11:29 ` [RFC PATCH v4 1/3] mac80211: use AQL airtime for expected throughput Baligh Gasmi
2022-06-01 11:29 ` [RFC PATCH v4 2/3] mac80211: add periodic monitor for channel busy time Baligh Gasmi
2022-06-21 7:28 ` Kalle Valo
2022-06-01 11:29 ` [RFC PATCH v4 3/3] mac80211: add busy time factor into expected throughput Baligh Gasmi
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=20220601112903.2346319-1-gasmibal@gmail.com \
--to=gasmibal@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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.