From: Lukasz Kucharczyk <lukasz.kucharczyk@tieto.com>
To: Marek Lindner <lindner_marek@yahoo.de>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC 0/2] bind RTS threshold to vif.
Date: Fri, 18 May 2012 09:26:21 +0200 [thread overview]
Message-ID: <4FB5F99D.1040707@tieto.com> (raw)
In-Reply-To: <201205171940.42671.lindner_marek@yahoo.de>
On 05/17/2012 01:40 PM, Marek Lindner wrote:
> On Thursday, May 17, 2012 17:58:41 Lukasz Kucharczyk wrote:
>> following patches bind rts threshold to vif.
>> I think it might be useful in multi channel operation
>> (one chip handling multiple virtual interfaces on different
>> channels).
>>
>> RTS threshold is still set with NL80211_CMD_SET_WIPHY, and can
>> be now executed for both hw and vif, so it's backward compatible
>> (from userspace).
>
> As much as I like the idea of having per vif rts/cts settings, the rts/cts
> user space API is useless as long as these settings are bluntly ignored by
> certain rate control algorithms. I already had to explain to a dozen people
> who turned rts/cts off via this API does not really turn it off.
> Therefore, I suggest to remove the rts/cts API altogether, so that nobody
> falls into the trap of believing this does anything useful.
Oops, I totally missed IEEE80211_TX_RC_USE_RTS_CTS. Thanks for comment!
BR,
Lukasz
prev parent reply other threads:[~2012-05-18 7:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 9:58 [RFC 0/2] bind RTS threshold to vif Lukasz Kucharczyk
2012-05-17 9:58 ` [RFC 1/2] cfg80211/mac80211: " Lukasz Kucharczyk
2012-05-17 9:58 ` [RFC 2/2] iw: handle rts threshold per netdev Lukasz Kucharczyk
2012-05-17 11:40 ` [RFC 0/2] bind RTS threshold to vif Marek Lindner
2012-05-18 7:26 ` Lukasz Kucharczyk [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=4FB5F99D.1040707@tieto.com \
--to=lukasz.kucharczyk@tieto.com \
--cc=lindner_marek@yahoo.de \
--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.