From: Kalle Valo <kvalo@kernel.org>
To: Baligh Gasmi <gasmibal@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"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
Subject: Re: [RFC PATCH v4 2/3] mac80211: add periodic monitor for channel busy time
Date: Tue, 21 Jun 2022 10:28:11 +0300 [thread overview]
Message-ID: <87r13ipjas.fsf@kernel.org> (raw)
In-Reply-To: <20220601112903.2346319-3-gasmibal@gmail.com> (Baligh Gasmi's message of "Wed, 1 Jun 2022 13:29:02 +0200")
Baligh Gasmi <gasmibal@gmail.com> writes:
> Add a worker scheduled periodicaly to calculate the busy time average of
> the current channel.
>
> This will be used in the estimation for expected throughput.
>
> Signed-off-by: Baligh Gasmi <gasmibal@gmail.com>
[...]
> --- a/net/mac80211/iface.c
> +++ b/net/mac80211/iface.c
> @@ -1970,6 +1970,64 @@ static void ieee80211_assign_perm_addr(struct ieee80211_local *local,
> mutex_unlock(&local->iflist_mtx);
> }
>
> +#define DEFAULT_MONITOR_INTERVAL_MS 1000
I'm worried that polling every second affects power consumption.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-06-21 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 11:29 [RFC PATCH v4 0/3] expected throughput from AQL airtime Baligh Gasmi
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 [this message]
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=87r13ipjas.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gasmibal@gmail.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 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).