From: Felix Fietkau <nbd@openwrt.org>
To: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] ath9k: Choose highest rate of MRR based on IEEE80211_TX_CTL_USE_MINRATE
Date: Thu, 29 Sep 2011 15:06:23 +0200 [thread overview]
Message-ID: <4E846D4F.1070900@openwrt.org> (raw)
In-Reply-To: <20110929121426.GA20802@vmraj-lnx.users.atheros.com>
On 2011-09-29 2:14 PM, Rajkumar Manoharan wrote:
> On Thu, Sep 29, 2011 at 01:32:03PM +0200, Felix Fietkau wrote:
>> On 2011-09-29 1:24 PM, Rajkumar Manoharan wrote:
>> >Select appropriate rate as highest rate of rate series, if the frame
>> >was asked to be sent at minimum rate. For example nullfunc frames
>> >either can be sent at HT rates on normal case or at non-HT rates if
>> >it is used for connection monitoring.
>> >
>> >Signed-off-by: Rajkumar Manoharan<rmanohar@qca.qualcomm.com>
>> >---
>> > drivers/net/wireless/ath/ath9k/rc.c | 4 ++--
>> > 1 files changed, 2 insertions(+), 2 deletions(-)
>> >
>> Shouldn't the check for IEEE80211_TX_CTL_USE_MINRATE be in
>> rate_control_send_low(), so that it does not have to be repeated in
>> every single rate control module?
>>
> But I donno what could be the side effect of changing rate_control_send_low
> as it is used by all drivers. And also if the rate control provide the
> minrate, it can be used to update the PER upon tx status. isnt it?
It always updates the PER upon tx status, even if rate_control_send_low
was used. It should work the same way for every driver, so I think
putting this in the ath9k rc is the wrong place, and it would be weird
if a flag with such a generic name as IEEE80211_TX_CTL_USE_MINRATE would
be used by some rate control modules and ignored by others.
- Felix
next prev parent reply other threads:[~2011-09-29 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 11:24 [PATCH 2/2] ath9k: Choose highest rate of MRR based on IEEE80211_TX_CTL_USE_MINRATE Rajkumar Manoharan
2011-09-29 11:32 ` Felix Fietkau
2011-09-29 12:14 ` Rajkumar Manoharan
2011-09-29 13:06 ` Felix Fietkau [this message]
2011-09-29 13:37 ` Rajkumar Manoharan
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=4E846D4F.1070900@openwrt.org \
--to=nbd@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rmanohar@qca.qualcomm.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 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.