From: Johannes Berg <johannes@sipsolutions.net>
To: Tamizh chelvam <tamizhr@codeaurora.org>, ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCHv6 6/9] mac80211: Add api to support configuring TID specific configuration
Date: Wed, 31 Jul 2019 11:34:07 +0200 [thread overview]
Message-ID: <7aa18e9e89743f3b4a188c8e677aad203a3ef2db.camel@sipsolutions.net> (raw)
In-Reply-To: <1560835632-17405-7-git-send-email-tamizhr@codeaurora.org>
On Tue, 2019-06-18 at 10:57 +0530, Tamizh chelvam wrote:
>
> @@ -1626,6 +1635,14 @@ struct ieee80211_vif {
>
> bool txqs_stopped[IEEE80211_NUM_ACS];
>
> + int noack[IEEE80211_TID_MAX];
> + int retry_short[IEEE80211_TID_MAX];
> + int retry_long[IEEE80211_TID_MAX];
> + int ampdu[IEEE80211_TID_MAX];
> + u8 rate_ctrl[IEEE80211_TID_MAX];
> + u32 rate_code[IEEE80211_TID_MAX];
> + u8 rtscts[IEEE80211_TID_MAX];
This is quite a bit of data (176 bytes), can we make it up to the driver
to store it if supported, instead?
> @@ -2004,6 +2027,13 @@ struct ieee80211_sta {
>
> struct ieee80211_txq *txq[IEEE80211_NUM_TIDS + 1];
>
> + int noack[IEEE80211_TID_MAX];
> + int retry_short[IEEE80211_TID_MAX];
> + int retry_long[IEEE80211_TID_MAX];
> + int ampdu[IEEE80211_TID_MAX];
> + u8 rate_ctrl[IEEE80211_TID_MAX];
> + u8 rtscts[IEEE80211_TID_MAX];
same here.
> +static int ieee80211_set_tid_config(struct wiphy *wiphy,
> + struct net_device *dev,
> + struct ieee80211_tid_config *tid_conf)
> +{
> + struct ieee80211_sub_if_data *sdata = IEEE80211_DEV_TO_SUB_IF(dev);
> + struct sta_info *sta;
> + int ret;
> +
> + if (!sdata->local->ops->set_tid_config)
> + return -EOPNOTSUPP;
> +
> + if (!tid_conf->peer)
> + return drv_set_tid_config(sdata->local, sdata, NULL, tid_conf);
> +
> + mutex_lock(&sdata->local->sta_mtx);
> +
> + sta = sta_info_get_bss(sdata, tid_conf->peer);
> + if (!sta) {
> + mutex_unlock(&sdata->local->sta_mtx);
> + return -ENOENT;
> + }
> +
> + ret = drv_set_tid_config(sdata->local, sdata, &sta->sta, tid_conf);
> + mutex_unlock(&sdata->local->sta_mtx);
> + return ret;
> +}
and you're not actually using the data anyway?
johannes
next prev parent reply other threads:[~2019-07-31 9:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 5:27 [PATCHv6 0/9] cfg80211/mac80211: Add support for TID specific configuration Tamizh chelvam
2019-06-18 5:27 ` [PATCHv6 1/9] nl80211: New netlink command " Tamizh chelvam
2019-07-11 12:51 ` Sergey Matyukevich
2019-07-31 10:04 ` Tamizh chelvam
2019-07-11 13:13 ` Sergey Matyukevich
2019-07-31 9:19 ` Johannes Berg
2019-07-31 10:28 ` Tamizh chelvam
2019-07-31 9:25 ` Johannes Berg
2019-08-10 12:40 ` Tamizh chelvam
2019-08-21 7:42 ` Johannes Berg
2019-06-18 5:27 ` [PATCHv6 2/9] nl80211: Add new netlink attribute for TID speicific retry count Tamizh chelvam
2019-07-31 9:24 ` Johannes Berg
2019-08-10 12:06 ` Tamizh chelvam
2019-08-21 7:41 ` Johannes Berg
2019-06-18 5:27 ` [PATCHv6 3/9] nl80211: Add netlink attribute for AMPDU aggregation enable/disable Tamizh chelvam
2019-07-31 9:28 ` Johannes Berg
2019-08-10 12:41 ` Tamizh chelvam
2019-06-18 5:27 ` [PATCHv6 4/9] nl80211: Add netlink attribute to enable/disable RTS_CTS Tamizh chelvam
2019-06-18 5:27 ` [PATCHv6 5/9] nl80211: Add netlink attribute to configure TID specific tx rate Tamizh chelvam
2019-07-11 12:54 ` Sergey Matyukevich
2019-07-31 10:08 ` Tamizh chelvam
2019-07-31 9:32 ` Johannes Berg
2019-06-18 5:27 ` [PATCHv6 6/9] mac80211: Add api to support configuring TID specific configuration Tamizh chelvam
2019-07-31 9:34 ` Johannes Berg [this message]
2019-06-18 5:27 ` [PATCHv6 7/9] ath10k: Add wmi command support for station specific TID config Tamizh chelvam
2019-06-18 5:27 ` [PATCHv6 8/9] ath10k: Add new api to support TID specific configuration Tamizh chelvam
2019-06-18 5:27 ` [PATCHv6 9/9] ath10k: Add extended TID configuration support Tamizh chelvam
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=7aa18e9e89743f3b4a188c8e677aad203a3ef2db.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tamizhr@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).