From: Kalle Valo <kvalo@codeaurora.org>
To: <pkshih@realtek.com>
Cc: <Larry.Finger@lwfinger.net>, <yhchuang@realtek.com>,
<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 05/10] rtlwifi: enable mac80211 fast-tx support
Date: Tue, 16 Jan 2018 17:45:27 +0200 [thread overview]
Message-ID: <871sip24fc.fsf@purkki.adurom.net> (raw)
In-Reply-To: <20180111070932.9929-6-pkshih@realtek.com> (pkshih@realtek.com's message of "Thu, 11 Jan 2018 15:09:27 +0800")
<pkshih@realtek.com> writes:
> From: Ping-Ke Shih <pkshih@realtek.com>
>
> To enable the mac80211 fast-tx feature, the hw/driver needs to support
> dynamic power saving and fragmentation. Since our driver does not
> need to fragment packet into smaller pieces, we just hook an empty
> callback of set_frag_threshold to avoid fragmentation in mac80211.
>
> After this, the mac80211 will not fragment the packets and can transmit
> them faster by cache the header information.
>
> Signed-off-by: Yan-Hsuan Chuang <yhchuang@realtek.com>
> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
[...]
> --- a/drivers/net/wireless/realtek/rtlwifi/core.c
> +++ b/drivers/net/wireless/realtek/rtlwifi/core.c
> @@ -1001,6 +1001,11 @@ static void rtl_op_sta_statistics(struct ieee80211_hw *hw,
> sinfo->filled = 0;
> }
>
> +static int rtl_op_set_frag_threshold(struct ieee80211_hw *hw, u32 value)
> +{
> + return -EOPNOTSUPP;
> +}
> +
> /*
> *for mac80211 VO = 0, VI = 1, BE = 2, BK = 3
> *for rtl819x BE = 0, BK = 1, VI = 2, VO = 3
> @@ -1906,6 +1911,7 @@ const struct ieee80211_ops rtl_ops = {
> .configure_filter = rtl_op_configure_filter,
> .set_key = rtl_op_set_key,
> .sta_statistics = rtl_op_sta_statistics,
> + .set_frag_threshold = rtl_op_set_frag_threshold,
This also looks fishy, I guess there's a good reason why mac80211
requires set_frag_threshold()? To me this is just a workaround for a
mac80211 test.
--
Kalle Valo
next prev parent reply other threads:[~2018-01-16 15:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 7:09 [PATCH v2 00/10] rtlwifi: fix some bugs and add btcoex functions pkshih
2018-01-11 7:09 ` [PATCH v2 01/10] rtlwifi: Use mutex to replace spin_lock to protect IPS and LPS pkshih
2018-01-12 19:36 ` Larry Finger
2018-01-11 7:09 ` [PATCH v2 02/10] rtlwifi: fix scan channel 1 fail after IPS pkshih
2018-01-15 18:49 ` Larry Finger
2018-01-11 7:09 ` [PATCH v2 03/10] rtlwifi: Add sta_statistics of mac80211's op, and set filled=0 by default pkshih
2018-01-15 18:51 ` Larry Finger
2018-01-16 15:42 ` Kalle Valo
2018-01-16 22:06 ` Johannes Berg
2018-01-11 7:09 ` [PATCH v2 04/10] rtlwifi: unlink bss when un-association pkshih
2018-01-15 18:53 ` Larry Finger
2018-01-11 7:09 ` [PATCH v2 05/10] rtlwifi: enable mac80211 fast-tx support pkshih
2018-01-15 18:54 ` Larry Finger
2018-01-16 15:45 ` Kalle Valo [this message]
2018-01-16 20:12 ` Arend van Spriel
2018-01-16 22:24 ` Johannes Berg
2018-01-17 8:37 ` Arend van Spriel
2018-01-17 8:43 ` Johannes Berg
2018-01-18 9:05 ` Pkshih
2018-01-18 10:09 ` Johannes Berg
2018-01-19 1:39 ` Pkshih
2018-01-11 7:09 ` [PATCH v2 06/10] rtlwifi: Support A-MSDU in A-MPDU capability pkshih
2018-01-15 18:55 ` Larry Finger
2018-01-11 7:09 ` [PATCH v2 07/10] rtlwifi: btcoex: Add power_on_setting routine pkshih
2018-01-15 19:19 ` Larry Finger
2018-01-16 1:28 ` Pkshih
2018-01-11 7:09 ` [PATCH v2 08/10] rtlwifi: btcoex: Remove global variables from btcoex pkshih
2018-01-15 19:02 ` Larry Finger
2018-01-11 7:09 ` [PATCH v2 09/10] rtlwifi: btcoex: Add common function for qeurying BT information pkshih
2018-01-15 19:15 ` Larry Finger
2018-01-16 0:55 ` Pkshih
2018-01-16 15:52 ` Kalle Valo
2018-01-16 17:02 ` Larry Finger
2018-01-11 7:09 ` [PATCH v2 10/10] rtlwifi: btcoex: add rfe_type parameter to btcoex pkshih
2018-01-15 19:17 ` Larry Finger
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=871sip24fc.fsf@purkki.adurom.net \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=yhchuang@realtek.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).