Linux wireless drivers development
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@nbd.name>
To: linux-wireless@vger.kernel.org
Cc: johannes@sipsolutions.net, toke@kernel.org
Subject: Re: [PATCH v2 1/4] mac80211: fix overflow issues in airtime fairness code
Date: Sat, 18 Jun 2022 10:51:18 +0200	[thread overview]
Message-ID: <bcdb70fe-de2f-a46b-66e2-ff92f8b86425@nbd.name> (raw)
In-Reply-To: <20220611200106.34319-1-nbd@nbd.name>

On 11.06.22 22:01, Felix Fietkau wrote:
> The airtime weight calculation overflows with a default weight value of 256
> whenever more than 8ms worth of airtime is reported.
> Bigger weight values impose even smaller limits on maximum airtime values.
> This can mess up airtime based calculations for drivers that don't report
> per-PPDU airtime values, but batch up values instead.
> 
> Fix this by reordering multiplications/shifts and by reducing unnecessary
> intermediate precision (which was lost in a later stage anyway).
> 
> The new shift value limits the maximum weight to 4096, which should be more
> than enough. Any values bigger than that will be rejected
> 
> Signed-off-by: Felix Fietkau <nbd@nbd.name>
Please don't merge this series yet. I'm still investigating reports of 
regressions caused by it.

- Felix

      parent reply	other threads:[~2022-06-18  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11 20:01 [PATCH v2 1/4] mac80211: fix overflow issues in airtime fairness code Felix Fietkau
2022-06-11 20:01 ` [PATCH v2 2/4] mac80211: improve AQL tx time estimation Felix Fietkau
2022-06-11 20:01 ` [PATCH v2 3/4] mac80211: fix ieee80211_txq_may_transmit regression Felix Fietkau
2022-06-11 20:01 ` [PATCH v2 4/4] mac80211: rework the airtime fairness implementation Felix Fietkau
2022-06-18  8:51 ` Felix Fietkau [this message]

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=bcdb70fe-de2f-a46b-66e2-ff92f8b86425@nbd.name \
    --to=nbd@nbd.name \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=toke@kernel.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