From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Justin Capella <justincapella@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] mac80211: Turn AQL into an NL80211_EXT_FEATURE
Date: Thu, 12 Dec 2019 11:29:55 +0100 [thread overview]
Message-ID: <871rt9g7ks.fsf@toke.dk> (raw)
In-Reply-To: <CAMrEMU9t-Ed9ASyjGcJvpKM=Japiy0fv_cd1_3D5Sy_UMte_9A@mail.gmail.com>
Justin Capella <justincapella@gmail.com> writes:
> Disclaimer: I'm new, so don't assume my questions are rhetorical...
>
> sta = container_of(txq->sta, struct sta_info, sta); // Is this
> correct?
Not sure what you're referring to here; but generally, yes? :)
> I see the use of IEEE80211_NUM_ACS seems to be standard, is that AC
> specific? I learned today that different devs have different numbers
> of queues...
AC numbers are defined in the standard, and there are always four of
them. Different hardware can have different numbers of queues, which may
or may not be related to NUM_ACS.
> What are the units of the THRESHOLD, iirc there was some bit
> shifting/masking?
Units are logically microseconds, but stored as increments of 4
microseconds because we ran out of bits; this is kept inside the
setter/getter function, though, so everywhere else is just microseconds.
> Is there supposed to be a queue per station, or just per interface?
There's a TXQ per TID (so 16 per station), and an additional one on the
interface for multicast.
> It seemed like the threshold was meant to pick a higher or lower
> queue, this seems to maybe just reject if not within the bounds?
There are two thresholds; one for the whole interface, and one per
station. If either is exceeded transmission will be throttled.
-Toke
next prev parent reply other threads:[~2019-12-12 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 14:52 [PATCH 0/2] mac80211: Turn AQL into a proper NL80211_EXT_FEATURE flag Toke Høiland-Jørgensen
2019-12-11 14:52 ` [PATCH 1/2] mac80211: Turn AQL into an NL80211_EXT_FEATURE Toke Høiland-Jørgensen
2019-12-11 21:21 ` Johannes Berg
2019-12-12 6:05 ` Justin Capella
2019-12-12 10:29 ` Toke Høiland-Jørgensen [this message]
2019-12-12 10:26 ` Toke Høiland-Jørgensen
2019-12-11 14:52 ` [PATCH 2/2] ath10k: Enable Airtime Queue Limits feature 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=871rt9g7ks.fsf@toke.dk \
--to=toke@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=justincapella@gmail.com \
--cc=linux-wireless@vger.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 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.